auto_approve
Whether specific MCP tools or entire servers can be configured for automatic approval without per-invocation user confirmation. Boundary: auto_approve governs execution gating (user prompt suppression) for tools that are already visible; see tool_filtering for tool visibility control.
Type: bool Content type: mcp
Provider Support
Section titled “Provider Support”| Provider | Supported | Mechanism |
|---|---|---|
| cline | ✓ | always_allow_tools (execution-gating scope): Cline's always_allow list suppresses per-invocation confirmation prompts for listed tools that are already visible |
| codex | ✓ | mcp_per_tool_approval: Codex supports per-tool approval configuration to suppress confirmation prompts for trusted tools |
| kiro | ✓ | kiro_mcp_auto_approve: Kiro supports per-server or per-tool auto-approval configuration to suppress confirmation prompts |
| roo-code | ✓ | always_allow_list: alwaysAllow tool names bypass confirmation prompts for that server |
| amp | ✗ | Amp does not document pre-configured auto-approval for specific MCP tools separate from tool filtering |
| claude-code | ✗ | Claude Code does not support pre-configured auto-approval for specific MCP tools; all tool calls require user confirmation unless covered by session permission rules |
| copilot-cli | ✗ | Copilot CLI does not document pre-configured auto-approval for MCP tools |
| crush | ✗ | Crush does not document pre-configured auto-approval for specific MCP tools |
| cursor | ✗ | Cursor does not document pre-configured auto-approval for specific MCP tools. |
| factory-droid | ✗ | Factory Droid does not document pre-configured auto-approval for MCP tools |
| gemini-cli | ✗ | Gemini CLI does not document pre-configured auto-approval for specific MCP tools |
| opencode | ✗ | not documented |
| windsurf | ✗ | Windsurf does not support pre-configured auto-approval for specific MCP tools |
| zed | ✗ | Zed does not document a pre-approved MCP tools list |