Roll dice using standard NdM+K notation, e.g. 2d6, 1d20+5, 4d8-2.
AI agents call roll_dice as a supporting operation in Dice Roller MCP Server workflows.
Without any rule in front of it, every call an agent makes to roll_dice happens silently — no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
Roll dice using standard NdM+K notation, e.g. 2d6, 1d20+5, 4d8-2. It is categorised as a Other tool in the Dice Roller MCP Server MCP Server, which means it performs auxiliary operations.
Register the Dice Roller 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 Roller MCP Server. Nothing to install.
roll_dice is a Other tool with low risk. Read-only tools are generally safe to allow by default.
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 Roller MCP Server MCP server (swayam-mishra/mcp). 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 →