AI agents call random_dice to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | integer | — | Number of dice to roll |
sides | integer | — | Number of sides on the die |
Parameters from the server's own tool schema.
This tool generates random output (dice rolls) based on input parameters. It does not create, modify, delete, or execute operations on data stores or external systems. It has no persistent effects beyond returning a value to the caller, making it a read-only retrieval of generated data with negligible risk.
From the tool's definition Tool name 'random_dice' and description 'Roll dice with configurable sides' indicate a pure computation/simulation that returns random values with no side effects on external state or data persistence.
Attacks that exploit this kind of access
Roll dice with configurable sides. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_dice accepts 2 parameters: count, sides. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for random_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 TinyFn. Nothing to install.
random_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 random_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 random_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.
random_dice is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
random_dice is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →