Schedule the KMS key for a signer for deletion (7-day AWS minimum window). Refused if the signer has on-chain balance ≥ dust — drain first.
AI agents call delete_signer to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of a KMS signing key, which is a cryptographic credential. Once deleted, it cannot be recovered, and any funds or assets controlled by that signer become inaccessible (unless alternative keys exist).
From the tool's definition Tool name is 'delete_signer' and description states it schedules 'KMS key for a signer for deletion'. This irreversibly removes cryptographic signing capability.
Attacks that exploit this kind of access
Schedule the KMS key for a signer for deletion (7-day AWS minimum window). Refused if the signer has on-chain balance ≥ dust — drain first. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for delete_signer: 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.
delete_signer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_signer 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 delete_signer. 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.
delete_signer 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.
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 →