clear_status_effects

THE RISK

Critical Risk

Why clear_status_effects needs a policy

The tool irreversibly removes status effects from a character. While 'destructive' in the traditional sense applies to data deletion, removing all status effects is a non-reversible in-game state change (effects are gone unless re-applied). However, the blast radius is low since this is confined to a text-based RPG game state with no real-world consequences.

From the tool's definition Remove all status effects from a character (or filter by type/name)

Documented attack patterns abuse exactly the kind of access clear_status_effects gives an agent:

POLICY

How to control clear_status_effects

PolicyLayer is an MCP gateway — it sits between your AI agents and DMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_status_effects:

policy.json

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

clear_status_effects disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register DMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DMCP tools

Destructive cancel_event Cancel a scheduled event Destructive clear_pause_state Clear the saved pause state for a game. Use after successfully resuming to start fresh. Destructive delete_ability Delete an ability Destructive delete_audio Delete a stored audio file (removes file and database record) Destructive delete_character Delete a character permanently. This is IRREVERSIBLE and will remove the character and all Destructive delete_external_update Delete an external update entirely. Destructive delete_faction Delete a faction Destructive delete_game Delete a game and all its data. This is IRREVERSIBLE and removes all characters, locations

All 204 DMCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in DMCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clear_status_effects

What does the clear_status_effects tool do? +

Remove all status effects from a character (or filter by type/name). It is categorised as a Destructive tool in the DMCP 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 clear_status_effects? +

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

What risk level is clear_status_effects? +

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

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

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

clear_status_effects is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DMCP tool call.

Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →