set_recovery_address · Run402 MCP: Risk & Policy

WHAT IT DOES

What set_recovery_address does on Run402

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

WHY IT NEEDS A POLICY

Why set_recovery_address needs a policy

This tool writes/modifies data (recovery address configuration) that is reversible but has high severity implications. It controls where funds or sensitive operations may be redirected during KMS signer deletion on day-90. While not immediately destructive (the address can be changed/cleared), misconfiguration could lead to loss of access to recovery mechanisms or misdirection of auto-drain operations.

From the tool's definition 'Set or clear the optional recovery address' indicates modification of a critical security setting (KMS signer recovery mechanism). The tool modifies a recovery configuration that affects KMS signer deletion behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_recovery_address Rate-limited

set_recovery_address 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": {
    "set_recovery_address": {
      "limits": [
        {
          "counter": "set_recovery_address_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 Run402, so you can run agents against it safely.

FAQ

Questions about set_recovery_address

What does the set_recovery_address tool do? +

Set or clear the optional recovery address used for auto-drain on day-90 deletion of a KMS signer. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_recovery_address? +

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

What risk level is set_recovery_address? +

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

Can I rate-limit set_recovery_address? +

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

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

set_recovery_address is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.