urwa_is_kill_switched
A other tool on the Tenzro Ledger MCP server.
This record as markdown: /tools/network-tenzro-tenzro/urwa-is-kill-switched.md
What urwa_is_kill_switched does on Tenzro Ledger MCP
AI agents call urwa_is_kill_switched as a supporting operation in Tenzro Ledger MCP workflows.
Why urwa_is_kill_switched is rated Low
The name implies a status check (Read), but 'kill switch' could also imply a state change or destructive capability. With no description, confidence is low. Given the financial/critical context of the server (wallet, payments, staking), even a read on a kill switch could have significant implications, but without evidence of action, defaulting to Read with medium severity.
From the tool's definition Tool name 'urwa_is_kill_switched' suggests checking a kill switch status (a read/query operation), but the description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs urwa_is_kill_switched 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_is_kill_switched, this is the rule to start with:
urwa_is_kill_switched gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every urwa_is_kill_switched call is checked against it from then on.
Questions about urwa_is_kill_switched
urwa_is_kill_switched is a other tool on the Tenzro Ledger MCP server. It is categorised as a Other tool in the Tenzro Ledger MCP MCP Server, which means it performs auxiliary operations.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for urwa_is_kill_switched: 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_is_kill_switched is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the urwa_is_kill_switched 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_is_kill_switched. 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_is_kill_switched 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.
This server
Across the catalogue