Answer: In Zed v0.224.0 and above, tool approval is controlled by the `agent.tool_permissions.default` setting, which can be set to "confirm" (default), "allow", or "deny". For granular control over specific MCP tools, you can configure per-tool permission rules using the key format `mcp::`, with the `default` key on a per-tool entry being the primary mechanism for MCP tools. Status: Overdue (check was due 2026-11-20T13:38:36Z and has not succeeded) Entry: tool/zed/permissions-and-security/mcp-tool-permissions Revision: 1 Digest: sha256:2ebb7e83fd26d6d2 (changes whenever the content changes) Timeline: Created: 2026-11-13T04:00:11Z Last changed: 2026-11-13T04:00:11Z Last verified: 2026-11-19T13:38:36Z Next check: 2026-11-20T13:38:36Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of setting | agent.tool_permissions.default | [1] | 2026-11-19 version | v0.224.0 | [1] | 2026-11-19 allow option | "allow" | [1] | 2026-11-19 deny option | "deny" | [1] | 2026-11-19 per-tool key format | mcp:: | [1] | 2026-11-19 example key | mcp:github:create_issue | [1] | 2026-11-19 legacy setting | agent.always_allow_tool_actions | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/ai/mcp.md". https://zed.dev/docs/ai/mcp.md Role: primary. Accessed: 2026-11-19T13:38:36Z Quote: "tool approval is controlled by `agent.tool_permissions.default`" (Supports: setting) Quote: "In Zed v0.224.0 and above, tool approval is controlled by" (Supports: version) Quote: "`"allow"` — Auto-approves tool actions without prompting" (Supports: allow option) Quote: "`"deny"` — Blocks all tool actions" (Supports: deny option) Quote: "MCP tools use the key format `mcp::`" (Supports: per-tool key format) Quote: "for example, `mcp:github:create_issue`" (Supports: example key) Quote: "In earlier versions, it was controlled by the `agent.always_allow_tool_actions` boolean (default `false`)." (Supports: legacy setting) Snapshot SHA-256: 4b63e4863aff99eac69af64220581c36f8becd856cb3d11fb811f038881615bf (captured 2026-11-13T04:00:11Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T04:00:11Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:38:36Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:38:36Z Last attempt: 2026-11-19T13:38:36Z Notes and limitations: Extracted automatically from a single official source (section "Tool Permissions"). Human-readable page: https://zed.dev/docs/ai/mcp.html Related: https://latestn.com/tool/zed/permissions-and-security/persistent-sandbox-permissions How do I manage persistent sandbox permissions in Zed? https://latestn.com/tool/zed/permissions-and-security/process-exec-capability What does the process:exec capability allow a Zed extension to do? https://latestn.com/tool/zed/permissions-and-security/profiles-vs-tool-permissions What is the difference between Zed agent profiles and tool permissions? https://latestn.com/tool/zed/permissions-and-security/disable-all-extension-capabilities How do I disable all capabilities for Zed extensions? https://latestn.com/tool/zed/permissions-and-security/download-file-capability What does the download_file capability allow a Zed extension to do? https://latestn.com/tool/zed/permissions-and-security/invite-manage-channel-members How do I invite people to a Zed channel and manage members? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:00:11Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/permissions-and-security/mcp-tool-permissions/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/permissions-and-security/mcp-tool-permissions POST: https://latestn.com/dispute/tool/zed/permissions-and-security/mcp-tool-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/permissions-and-security/mcp-tool-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure tool permissions for MCP servers in Zed? Revision 1, last verified 2026-11-19T13:38:36Z. https://latestn.com/tool/zed/permissions-and-security/mcp-tool-permissions (accessed 2026-11-21T10:07:11Z). @misc{LatestN_tool_zed_permissions_and_security_mcp_tool_permissions_r1, title = {How do I configure tool permissions for MCP servers in Zed?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/permissions-and-security/mcp-tool-permissions}}, note = {Revision 1; digest sha256:2ebb7e83fd26d6d2; last verified 2026-11-19T13:38:36Z; accessed 2026-11-21T10:07:11Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/permissions-and-security/mcp-tool-permissions