Delete a character permanently. This is IRREVERSIBLE and will remove the character and all associated data.
AI agents call delete_character 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.
This tool permanently removes data (a character and all associated data) without the ability to undo the action. While the blast radius is limited to game state within an RPG context (not production systems or financial data), the irreversible nature of deletion and emphasis on permanence and irreversibility places it firmly in the Destructive category rather than Write.
From the tool's definition Tool description explicitly states 'Delete a character permanently' and 'IRREVERSIBLE and will remove the character and all associated data.' The name 'delete_character' combined with irreversible data removal clearly indicates destructive capability.
Documented attack patterns abuse exactly the kind of access delete_character 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 delete_character:
{
"version": "1",
"default": "deny",
"hide": [
"delete_character"
]
}delete_character 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.
Delete a character permanently. This is IRREVERSIBLE and will remove the character and all associated data. 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 delete_character: 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.
delete_character 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 delete_character 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 delete_character. 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.
delete_character 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.