{"version":"2.1.191","anchor":"mcp-tool-level-permission-policies","canonical_anchor":"mcp-tool-level-permission-policies","heading":"MCP Tool-Level Permission Policies","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191\/e\/mcp-tool-level-permission-policies","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191","markdown":"### MCP Tool-Level Permission Policies\n\n**What**\n\nIndividual MCP tools can now declare a `permission_policy` in the MCP server config, allowing fine-grained pre-authorization without manual approval prompts.\n\n**Usage**\n\nSet `permission_policy` on any tool entry in your MCP server configuration:\n\n`{ \"mcpServers\": { \"myserver\": { \"type\": \"http\", \"url\": \"http:\/\/localhost:3000\", \"tools\": [ { \"name\": \"read_db\", \"permission_policy\": \"always_allow\" }, { \"name\": \"write_db\", \"permission_policy\": \"always_ask\" }, { \"name\": \"drop_db\", \"permission_policy\": \"always_deny\" } ] } } }` **Details** - Accepted values: `always_allow`, `always_ask`, `always_deny`. - Policies are translated to `mcpServerPolicy` entries in the effective allow\/ask\/deny rule sets. - Only applies to `http` and `sse` transport types; stdio tools are unaffected. - Overrides the default prompt-based approval flow for that specific tool. **Evidence** MCP permission policy resolver (search for `\"permission_policy\"` alongside `\"always_allow\"`)"}