urwa_trigger_kill_switch
(Admin) Activate the ERC-7943 kill-switch on a token.
This record as markdown: /tools/network-tenzro-tenzro/urwa-trigger-kill-switch.md
What urwa_trigger_kill_switch does on Tenzro Ledger MCP
AI agents call urwa_trigger_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.
Why urwa_trigger_kill_switch is rated Critical
A kill-switch on a token is an irreversible or highly severe administrative action that disables/freezes/destroys token functionality. This is a destructive operation with critical blast radius — misuse could halt all transfers or destroy token utility for all holders. It also has financial implications (token value/usability), but the primary nature is a destructive system-level action.
From the tool's definition Activate the ERC-7943 kill-switch on a token
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs urwa_trigger_kill_switch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For urwa_trigger_kill_switch, this is the rule to start with:
urwa_trigger_kill_switch is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every urwa_trigger_kill_switch call is checked against it from then on.
Questions about urwa_trigger_kill_switch
(Admin) Activate the ERC-7943 kill-switch on a token. 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_trigger_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_trigger_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_trigger_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_trigger_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_trigger_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.
More on Tenzro Ledger, and thousands of servers like it.
Across the catalogue