end_combat · DM20 Protocol MCP: Risk & Policy

WHAT IT DOES

What end_combat does on DM20 Protocol

AI agents use end_combat to create or update resources in DM20 Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DM20 Protocol environment.

WHY IT NEEDS A POLICY

Why end_combat needs a policy

This tool terminates an active combat session, which is a state change (write operation) within the D&D campaign management system. It modifies the combat state from active to ended. While it changes game state, it is likely reversible by starting a new encounter, so it does not qualify as Destructive. The blast radius is medium since misuse could disrupt an ongoing combat session, losing tracking data.

From the tool's definition End the current combat encounter

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

end_combat Rate-limited

end_combat stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "end_combat": {
      "limits": [
        {
          "counter": "end_combat_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DM20 Protocol, so you can run agents against it safely.

FAQ

Questions about end_combat

What does the end_combat tool do? +

End the current combat encounter. It is categorised as a Write tool in the DM20 Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on end_combat? +

Register the DM20 Protocol MCP server in PolicyLayer and add a rule for end_combat: 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 DM20 Protocol. Nothing to install.

What risk level is end_combat? +

end_combat is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit end_combat? +

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

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

end_combat is provided by the DM20 Protocol MCP server (polloinfilzato/dm20-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.