Roll the dice with the given notation
AI agents call roll_dice to retrieve information from Tavily Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a local dice-roll simulation based on notation input (e.g., 'd20', '2d6+3'). It computes and returns a result without querying external systems, modifying state, executing arbitrary code, or causing side effects. While it doesn't strictly 'retrieve' data in the web-search sense, it fits best under Read as a non-destructive operation that returns information without side effects.
From the tool's definition Tool name 'roll_dice' with description 'Roll the dice with the given notation' indicates a computational operation that generates random values. No data retrieval, modification, deletion, code execution, or financial impact is described or implied.
Attacks that exploit this kind of access
Roll the dice with the given notation. It is categorised as a Read tool in the Tavily Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tavily Search 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 Tavily Search MCP Server. Nothing to install.
roll_dice is a Read 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 Tavily Search MCP Server MCP server (mwalker-tmd/mcp-session-code). 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 →