dice_notation_roll
Seeded Dice-Notation Roller — Roll tabletop dice notation ('2d6+3') deterministically from a required seed (sha256-derived, reproducible on any Python version) -- not wall-clock randomness.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/dice-notation-roll.md
What dice_notation_roll does on Gateway
AI agents invoke dice_notation_roll to trigger actions in Gateway. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
seed | integer | string | Yes | Seed for deterministic rolls (any integer or string) |
notation | string | Yes | Dice notation, e.g. '2d6+3', '1d20', 'd8-1' |
Parameters from the server's own tool schema.
Why dice_notation_roll is rated High
The tool runs a deterministic computation (SHA256-based dice roll simulation) triggered by user arguments. It doesn't merely retrieve stored data (Read) nor does it write/modify/delete anything. It executes a calculation process, making Execute the best fit. Blast radius is very low since it only produces a numeric result with no side effects.
From the tool's definition 'Roll tabletop dice notation' and 'deterministically from a required seed (sha256-derived)' — the tool executes a computation/calculation based on inputs
Attacks that exploit this kind of access
The rule that runs dice_notation_roll safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dice_notation_roll, this is the rule to start with:
dice_notation_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every dice_notation_roll call is checked against it from then on.
Questions about dice_notation_roll
Seeded Dice-Notation Roller — Roll tabletop dice notation ('2d6+3') deterministically from a required seed (sha256-derived, reproducible on any Python version) -- not wall-clock randomness. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
dice_notation_roll accepts 2 parameters: seed, notation. Required: seed, notation. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for dice_notation_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 Gateway. Nothing to install.
dice_notation_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_notation_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_notation_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_notation_roll is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue