Critical Risk →

delete_faction

Delete a faction

How to control delete_faction ↓

What delete_faction does on DMCP

AI agents call delete_faction 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.

Critical Risk

Why delete_faction needs a policy

This tool permanently removes a faction from the game state without possibility of recovery within the game context. While the blast radius is limited to a single game session (not production data or financial systems), deleting a faction could destroy significant game progress, narrative elements, or player investments in that faction's storyline.

From the tool's definition Tool name is 'delete_faction' with description 'Delete a faction'. The word 'delete' indicates irreversible removal of game state data.

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

How to control delete_faction

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_faction:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_faction"
  ]
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_faction

What does the delete_faction tool do? +

Delete a faction. 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 delete_faction? +

Register the D MCP server in PolicyLayer and add a rule for delete_faction: 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 delete_faction? +

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

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

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

delete_faction 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.

Free to start. No card required.

204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.