<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Security - Sonny</title><link>https://sonny.sh/tags/security/</link><description>Recent content on Security</description><generator>Hugo 0.139.4</generator><language>en-us</language><lastBuildDate>Sat, 24 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sonny.sh/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP Trust Model</title><link>https://sonny.sh/docs/mcp/trust-model/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://sonny.sh/docs/mcp/trust-model/</guid><category>mcp</category><category>security</category><category>reference</category><description> MCP Trust Model Share link Share this section Permalink Share via Twitter LinkedIn Facebook A configured MCP server is not an approved MCP server. Configuration says what exists; approval decides what runs. Two gates sit between them, and both apply to every surface that enumerates tools — a TUI tab, a headless run, a sub-agent, sonny mcp list --connect, sonny tools list --mcp-config and sonny recipe resolve --connect. A surface that can only list tools is not a way around either gate.</description></item></channel></rss>