urwa_trigger_kill_switch

(Admin) Activate the ERC-7943 kill-switch on a token.

Server Tenzro Ledger MCP https://canton-mcp.tenzro.network/mcp
Category Destructive
Risk class Critical
Parameters 00 required

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 needs a policy

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

Questions about urwa_trigger_kill_switch

What does the urwa_trigger_kill_switch tool do? +

(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.

How do I enforce a policy on urwa_trigger_kill_switch? +

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.

What risk level is urwa_trigger_kill_switch? +

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.

Can I rate-limit urwa_trigger_kill_switch? +

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.

How do I block urwa_trigger_kill_switch completely? +

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.

What MCP server provides urwa_trigger_kill_switch? +

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.

// THE FULL RECORD

urwa_trigger_kill_switch is one line of Tenzro Ledger'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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.