start_claudmaster_session
AI agents invoke start_claudmaster_session 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.
The 'start_' prefix and '_session' suffix indicate this tool triggers an operation rather than passively reads data. In D&D campaign management, starting a session likely initializes game state, activates tracking systems, or modifies the active game context. Without explicit description, it cannot be classified as Read (no retrieval indicated). It is not clearly Destructive or Financial.
From the tool's definition Tool name 'start_claudmaster_session' indicates initiation of a game session with potential state changes. Description is empty, limiting direct evidence.
Attacks that exploit this kind of access
start_claudmaster_session. 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_claudmaster_session: 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_claudmaster_session 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_claudmaster_session 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_claudmaster_session. 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_claudmaster_session 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 →