start_party_mode
AI agents invoke start_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.
Without a description, confidence is reduced. However, the naming pattern and server context suggest this tool triggers an operation (mode activation) rather than simple data retrieval or modification. Mode-switching in a multiplayer D&D context can trigger cascading effects on game state, NPCs, and player interaction rules.
From the tool's definition Tool name 'start_party_mode' lacks a description, but within the context of a D&D campaign management server, 'start_party_mode' likely triggers state transitions or initiates game sessions that affect shared game state.
Attacks that exploit this kind of access
start_party_mode. 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.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for start_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.
start_party_mode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_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.
Set action: deny in the PolicyLayer policy for start_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.
start_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →