Clear the saved pause state for a game. Use after successfully resuming to start fresh.
AI agents call clear_pause_state 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.
Clearing the pause state removes saved game progress data that cannot be recovered. While the description suggests it should only be called after successfully resuming (implying the data is no longer needed), the action itself is irreversible — the saved pause state is permanently deleted.
From the tool's definition 'Clear the saved pause state' and 'start fresh' indicate irreversible removal of stored pause/resume game state data
Documented attack patterns abuse exactly the kind of access clear_pause_state 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 clear_pause_state:
{
"version": "1",
"default": "deny",
"hide": [
"clear_pause_state"
]
} clear_pause_state 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.
Clear the saved pause state for a game. Use after successfully resuming to start fresh. 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 clear_pause_state: 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.
clear_pause_state 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 clear_pause_state 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 clear_pause_state. 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.
clear_pause_state 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.