circuit_breaker_record_success · Agent Runtime MCP

WHAT IT DOES

What circuit_breaker_record_success does on Agent Runtime

AI agents use circuit_breaker_record_success to create or update resources in Agent Runtime — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Runtime environment.

WHY IT NEEDS A POLICY

Why circuit_breaker_record_success needs a policy

This tool writes/updates state by recording a success event for a circuit breaker, modifying its internal counters or state. It is reversible in nature (state can be updated again) and has limited blast radius — misuse might incorrectly influence circuit breaker open/close decisions, but does not delete data or execute arbitrary code.

From the tool's definition Record a success for a circuit breaker

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

circuit_breaker_record_success Rate-limited

circuit_breaker_record_success stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "circuit_breaker_record_success": {
      "limits": [
        {
          "counter": "circuit_breaker_record_success_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Agent Runtime, so you can run agents against it safely.

FAQ

Questions about circuit_breaker_record_success

What does the circuit_breaker_record_success tool do? +

Record a success for a circuit breaker. It is categorised as a Write tool in the Agent Runtime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on circuit_breaker_record_success? +

Register the Agent Runtime MCP server in PolicyLayer and add a rule for circuit_breaker_record_success: 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.

What risk level is circuit_breaker_record_success? +

circuit_breaker_record_success is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit circuit_breaker_record_success? +

Yes. Add a rate_limit block to the circuit_breaker_record_success 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.

How do I block circuit_breaker_record_success completely? +

Set action: deny in the PolicyLayer policy for circuit_breaker_record_success. 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.

What MCP server provides circuit_breaker_record_success? +

circuit_breaker_record_success 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.