remove_deafness_by_caster

Exercise the original caster

SERVERTorch-to-Crown SOURCEDiogenes187/Torch-to-Crown

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/torch-to-crown/remove-deafness-by-caster.md

WHAT IT DOES

What remove_deafness_by_caster does on Torch-to-Crown

AI agents call remove_deafness_by_caster to permanently remove resources in Torch-to-Crown, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_deafness_by_caster is rated Critical

An AI agent that decides to call remove_deafness_by_caster doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Torch-to-Crown is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_deafness_by_caster safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Torch-to-Crown, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_deafness_by_caster, this is the rule to start with:

remove_deafness_by_caster Hidden

remove_deafness_by_caster is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_deafness_by_caster"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Torch-to-Crown, apply this rule, and every remove_deafness_by_caster call is checked against it from then on.

FAQ

Questions about remove_deafness_by_caster

What does the remove_deafness_by_caster tool do? +

Exercise the original caster. It is categorised as a Destructive tool in the Torch-to-Crown 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 remove_deafness_by_caster? +

Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for remove_deafness_by_caster: 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 Torch-to-Crown. Nothing to install.

What risk level is remove_deafness_by_caster? +

remove_deafness_by_caster 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 remove_deafness_by_caster? +

Yes. Add a rate_limit block to the remove_deafness_by_caster 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 remove_deafness_by_caster completely? +

Set action: deny in the PolicyLayer policy for remove_deafness_by_caster. 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 remove_deafness_by_caster? +

remove_deafness_by_caster is provided by the Torch-to-Crown MCP server (Diogenes187/Torch-to-Crown). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Torch-to-Crown, and thousands of servers like it.

This server

All 451 Torch-to-Crown tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →