Roll dice using standard TRPG notation. Supports modifiers,
AI agents invoke roll_dice to trigger actions in Dice MCP Server. 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.
Rolling dice involves executing a computation/random operation based on input arguments (dice notation, modifiers). It has no persistent side effects beyond potentially logging to history, making it low severity. It fits Execute rather than Read because it performs an operation rather than merely retrieving existing data.
From the tool's definition 'Roll dice using standard TRPG notation. Supports modifiers' — triggers a dice-rolling computation/operation with arguments determining the outcome
Attacks that exploit this kind of access
Roll dice using standard TRPG notation. Supports modifiers,. It is categorised as a Execute tool in the Dice MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dice MCP Server MCP server in PolicyLayer and add a rule for roll_dice: 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 Dice MCP Server. Nothing to install.
roll_dice 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 roll_dice 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 roll_dice. 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.
roll_dice is provided by the Dice MCP Server MCP server (patissiermongs/roleplayingmcp). 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 →