Roll the dice with the given notation
AI agents invoke roll_dice to trigger actions in AIE8-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 is a computational/execution action that produces a result based on input notation (e.g., '2d6'). It has no data persistence, financial impact, or destructive capability. It fits Execute because it performs an operation whose output depends on arguments, though the blast radius is minimal.
From the tool's definition "Roll the dice with the given notation" — executes a dice-rolling operation based on provided notation arguments
Attacks that exploit this kind of access
Roll the dice with the given notation. It is categorised as a Execute tool in the AIE8-MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AIE8-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 AIE8-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 AIE8-MCP Server MCP server (keertanachandar/aie8-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 →