reliability_reset · AgentPay MCP: Risk & Policy

WHAT IT DOES

What reliability_reset does on AgentPay

AI agents invoke reliability_reset to trigger actions in AgentPay. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why reliability_reset needs a policy

This tool forcibly resets a circuit breaker state, triggering an immediate operational change in infrastructure behavior. It doesn't merely read or write data — it executes a state transition that directly affects system reliability controls. Misuse could prematurely resume calls to a still-failing backend, causing cascading failures or unexpected financial charges from tool API calls resuming at scale.

From the tool's definition Force-close a tripped circuit breaker for a tool, allowing calls to resume immediately

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reliability_reset Rate-limited

reliability_reset stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reliability_reset": {
      "limits": [
        {
          "counter": "reliability_reset_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about reliability_reset

What does the reliability_reset tool do? +

Force-close a tripped circuit breaker for a tool, allowing calls to resume immediately. Use when a backend has recovered but the circuit hasn. It is categorised as a Execute tool in the AgentPay MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reliability_reset? +

Register the AgentPay MCP server in PolicyLayer and add a rule for reliability_reset: 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 AgentPay. Nothing to install.

What risk level is reliability_reset? +

reliability_reset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reliability_reset? +

Yes. Add a rate_limit block to the reliability_reset 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 reliability_reset completely? +

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

reliability_reset is provided by the AgentPay MCP server (joepangallo/mcp-server-agentpay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.