Drain a KMS signer
AI agents call drain_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.
Draining a KMS signer is a destructive, likely irreversible action. In the context of a payment/X402 infrastructure server (paid by X402, with financial tools like 'allowance_create'), a KMS signer likely holds private keys or signing authority for financial transactions. Draining it could mean emptying associated funds or destroying key material, making this at minimum Destructive and potentially Financial.
From the tool's definition 'Drain a KMS signer' — draining a KMS (Key Management Service) signer implies removing or exhausting the cryptographic key material or associated funds/resources from the signer, which is irreversible and catastrophic
Attacks that exploit this kind of access
Drain a KMS signer. 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 drain_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.
drain_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 drain_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 drain_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.
drain_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.
drain_signer is one line of Run402's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →