Get circuit breaker event history for an agent.
AI agents call circuit_breaker_events 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 and queries event history from a circuit breaker system. It performs a read-only operation ('Get') on existing data ('event history'). There is no modification, deletion, code execution, or financial impact. The tool is purely informational for monitoring and observability purposes, making it a standard Read category with low severity.
From the tool's definition Tool name 'circuit_breaker_events' and description 'Get circuit breaker event history for an agent' indicate a retrieval operation that queries historical data without modification or side effects.
Attacks that exploit this kind of access
Get circuit breaker event history 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_events: 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_events 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_events 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_events. 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_events 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 →