New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

urwa_clear_kill_switch

(Admin) Clear the ERC-7943 kill-switch on a token. Transfers resume.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/network-tenzro-tenzro/urwa-clear-kill-switch.md

What urwa_clear_kill_switch does on Tenzro Ledger MCP

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.

Why urwa_clear_kill_switch is rated Critical

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

Questions about urwa_clear_kill_switch

What does the urwa_clear_kill_switch tool do? +

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

How do I enforce a policy on urwa_clear_kill_switch? +

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.

What risk level is urwa_clear_kill_switch? +

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.

Can I rate-limit urwa_clear_kill_switch? +

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.

How do I block urwa_clear_kill_switch completely? +

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.

What MCP server provides urwa_clear_kill_switch? +

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.

More on Tenzro Ledger, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tenzro Ledger's. Pull the full record:

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.