Roll NdM and drop the lowest die, commonly used for stat rolling.
AI agents invoke roll_drop_lowest to trigger actions in Dice Roller 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.
This tool executes a dice-rolling mechanic (NdM notation with drop-lowest logic), which is an external operation whose result depends on arguments. It has no data read/write/delete implications and no financial impact. Severity is low because misuse only produces random numbers used for tabletop gaming purposes.
From the tool's definition 'Roll NdM and drop the lowest die' — triggers a dice-rolling computation/operation with real-time random number generation
Attacks that exploit this kind of access
Roll NdM and drop the lowest die, commonly used for stat rolling. It is categorised as a Execute tool in the Dice Roller MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dice Roller MCP Server MCP server in PolicyLayer and add a rule for roll_drop_lowest: 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_drop_lowest 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_drop_lowest 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_drop_lowest. 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_drop_lowest 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 →