Get the status of a circuit breaker for an agent.
AI agents call circuit_breaker_status to retrieve information from Agent Runtime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring/status information about circuit breaker state. It performs a query operation that does not modify, execute, delete, or commit any resources. The verb 'Get' and lack of any action language (create, update, delete, trigger, execute) confirm it is a Read operation.
From the tool's definition Tool name 'circuit_breaker_status' and description 'Get the status of a circuit breaker for an agent' indicate a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the status of a circuit breaker for an agent. It is categorised as a Read tool in the Agent Runtime MCP Server, which means it retrieves data without modifying state.
Register the Agent Runtime MCP server in PolicyLayer and add a rule for circuit_breaker_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Agent Runtime. Nothing to install.
circuit_breaker_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the circuit_breaker_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for circuit_breaker_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
circuit_breaker_status is provided by the Agent Runtime MCP server (marc-shade/agent-runtime-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →