combat_action · DM20 Protocol MCP: Risk & Policy

WHAT IT DOES

What combat_action does on DM20 Protocol

AI agents invoke combat_action to trigger actions in DM20 Protocol. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why combat_action needs a policy

The name 'combat_action' implies executing an in-game operation (applying combat rules, resolving attacks, etc.) rather than a simple read or write. Given sibling tools like 'apply_effect', 'build_encounter_tool', and 'add_death_save', this tool likely triggers game state changes during combat. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'combat_action' suggests triggering a game mechanic action, but the description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

combat_action Rate-limited

combat_action stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "combat_action": {
      "limits": [
        {
          "counter": "combat_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 combat_action

What does the combat_action tool do? +

combat_action. It is categorised as a Execute tool in the DM20 Protocol MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on combat_action? +

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

combat_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit combat_action? +

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

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

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