Roll dice using standard notation. IMPORTANT: For D&D advantage use
AI agents invoke dice_roll to trigger actions in Dice Rolling 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.
The tool executes a dice-rolling operation (a computation with external randomness), making it Execute category. It has no data persistence, financial implications, or destructive effects. Blast radius is very low as misuse can only produce random numbers, but it does perform an active operation rather than merely reading stored data.
From the tool's definition 'Roll dice using standard notation' — triggers a computation/execution that produces a random result using cryptographically secure randomness
Documented attack patterns abuse exactly the kind of access dice_roll gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dice Rolling MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dice_roll:
{
"version": "1",
"default": "deny",
"tools": {
"dice_roll": {
"limits": [
{
"counter": "dice_roll_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dice_roll 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.
Free to start. No card required.
Roll dice using standard notation. IMPORTANT: For D&D advantage use. It is categorised as a Execute tool in the Dice Rolling MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dice Rolling MCP Server MCP server in PolicyLayer and add a rule for dice_roll: 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 Rolling MCP Server. Nothing to install.
dice_roll 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 dice_roll 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 dice_roll. 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.
dice_roll is provided by the Dice Rolling MCP Server MCP server (jimmcq/dice-rolling-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dice Rolling MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Dice Rolling MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.