(Admin) Clear the ERC-7943 kill-switch on a token. Transfers resume.
AI agents call urwa_clear_kill_switch to permanently remove resources in Tenzro Ledger MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently disables a critical safety mechanism on a token, allowing transfers to resume. While not deleting data, it irreversibly removes a protective control and commits the system to an uncontrolled state.
From the tool's definition 'Clear the ERC-7943 kill-switch on a token. Transfers resume.' — This operation irreversibly removes a security control (kill-switch) that prevents token transfers, immediately re-enabling all transfers.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
(Admin) Clear the ERC-7943 kill-switch on a token. Transfers resume. It is categorised as a Destructive tool in the Tenzro Ledger MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for urwa_clear_kill_switch: 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 Tenzro Ledger MCP. Nothing to install.
urwa_clear_kill_switch 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 urwa_clear_kill_switch 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 urwa_clear_kill_switch. 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.
urwa_clear_kill_switch is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). 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 →