{"version":"2.1.302","anchor":"built-in-plugins-can-veto-mcp-servers","canonical_anchor":"built-in-plugins-can-veto-mcp-servers","heading":"Built-in plugins can refuse calls to their own MCP servers","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/built-in-plugins-can-veto-mcp-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Built-in plugins can refuse calls to their own MCP servers\n\nA built-in plugin can now refuse a call to an MCP server it provides, and the server is also refused if the plugin's check fails\n\n**What**\n\nAn MCP server is an add-on program that gives Claude extra tools. A built-in plugin, one that ships with Claude Code, can now refuse calls to an MCP server it provides. When it does, the call fails with a message saying the server was not called because the plugin that provides it refused this call.\n\nIf the plugin's own check fails with an error, the server is refused too.\n\n**Why**\n\nBuilt-in plugins can switch off their own MCP servers. If you see this message, the plugin that provides the server blocked the call, not your settings.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}