AI agents call delete_timer 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.
Deletion is inherently irreversible. While the blast radius is contextually limited to a single timer within a game session (not production data or user accounts), deletion operations are categorized as Destructive per the classification schema. In the context of RPG game state management, removing a timer could disrupt active gameplay mechanics, quests, or combat sequences depending on what the timer controls.
From the tool's definition Tool name explicitly uses "delete" verb and description states "Delete a timer". The irreversible removal of a game state element (a timer) qualifies as destructive action.
Documented attack patterns abuse exactly the kind of access delete_timer 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_timer:
{
"version": "1",
"default": "deny",
"hide": [
"delete_timer"
]
}delete_timer 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 timer. 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_timer: 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_timer 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_timer 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_timer. 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_timer 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.