Anthropic
Claude Managed Agents add an auto permission policy for agent and MCP tool calls, dated September 10, 2026
Claude's platform release notes, dated September 10, 2026, added an auto permission policy to Claude Managed Agents: the server evaluates each agent or MCP tool call and runs it, denies it, or pauses for approval. The agent.tool_use and agent.mcp_tool_use events now report that outcome in an evaluation field alongside evaluated_permission.
Claude's platform release notes, dated September 10, 2026, record a new
permission policy for Claude Managed Agents: "Claude Managed Agents
permission policies now include auto: the server evaluates each agent
or MCP tool call and runs it, denies it, or pauses for your approval.
agent.tool_use and agent.mcp_tool_use events report how each call
was evaluated in an evaluation field alongside evaluated_permission."
Claude's permission-policies documentation places auto alongside the
existing always_allow and always_ask policies, available to both the
agent toolset and MCP toolsets, with no toolset using it by default.
Under auto, a call runs "when the server determines that the call is
safe," is denied when "the server evaluates the call as high-risk," or
pauses for approval "when the server reaches no determination." Each
agent.tool_use and agent.mcp_tool_use event now carries
evaluated_permission ("allow", "ask", or "deny") and, in most
cases, an evaluation object naming the policy that produced that
outcome, with a reason_code attached when the outcome is ask or
deny.
Related publishers
How was this verified, and what are the sources?
Published · last verified · confidence 1.00.
- Claude Platform release notes, entry dated September 10, 2026 - "Claude Managed Agents permission policies now include auto: the server evaluates each agent or MCP tool call and runs it, denies it, or pauses for your approval. agent.tool_use and agent.mcp_tool_use events report how each call was evaluated in an evaluation field alongside evaluated_permission." - accessed
- Claude Platform docs, "Permission policies" - describes the three auto outcomes ("the call runs," "the call is denied," "the call pauses for your approval"), states no toolset uses auto by default, and documents the evaluated_permission values allow/ask/deny and the evaluation object's reason_code field - accessed