AI agents call remove_status_effect to permanently remove resources in DMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a status effect is a destructive operation within the game state management system; once removed, the effect is gone and cannot be undone without reapplication. However, the blast radius is confined to a text-based RPG game state, making the real-world severity low.
From the tool's definition "Remove a specific status effect" — the word 'remove' implies irreversible deletion of a status effect from game state
Documented attack patterns abuse exactly the kind of access remove_status_effect gives an agent:
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 remove_status_effect:
{
"version": "1",
"default": "deny",
"hide": [
"remove_status_effect"
]
}remove_status_effect disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a specific status effect. 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.
Register the D MCP server in PolicyLayer and add a rule for remove_status_effect: 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.
remove_status_effect is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_status_effect 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 remove_status_effect. 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.
remove_status_effect 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.
Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.