stop_party_mode · DM20 Protocol MCP: Risk & Policy

WHAT IT DOES

What stop_party_mode does on DM20 Protocol

AI agents invoke stop_party_mode 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 stop_party_mode needs a policy

This tool executes an operation with significant side effects: it terminates a web server and disconnects all players from an active D&D campaign session. While not destructive (the data persists), it is an Execute-category action because it triggers external operations whose consequences depend on execution context.

From the tool's definition Tool description explicitly states 'Stop the Party Mode web server and disconnect all players' — a direct command to terminate a running service and forcibly disconnect connected users.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_party_mode Rate-limited

stop_party_mode 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": {
    "stop_party_mode": {
      "limits": [
        {
          "counter": "stop_party_mode_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 stop_party_mode

What does the stop_party_mode tool do? +

Stop the Party Mode web server and disconnect all players. 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 stop_party_mode? +

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

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

Can I rate-limit stop_party_mode? +

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

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

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