This record as markdown: /tools/io-tinyfn-tinyfn/random-number.md
What random_number does on TinyFn
AI agents call random_number to retrieve information from TinyFn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | integer | — | How many numbers to generate |
max_val | integer | — | Maximum value (inclusive) |
min_val | integer | — | Minimum value (inclusive) |
Parameters from the server's own tool schema.
Why random_number is rated Low
This tool performs a deterministic-style computation (random number generation) entirely in-process. It reads no external data, writes nothing, executes no commands, and has no financial or destructive impact. The worst misuse is receiving an unexpected number. Slight confidence reduction because 'random' is non-deterministic despite the server claiming 500+ deterministic tools, but the risk remains low.
From the tool's definition Generate random integer(s) — purely generative/computational with no side effects, no external data access, no state modification.
Attacks that exploit this kind of access
The rule that runs random_number safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For random_number, this is the rule to start with:
random_number is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every random_number call is checked against it from then on.
Questions about random_number
Generate random integer(s). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_number accepts 3 parameters: count, max_val, min_val. 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_number: 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_number 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_number 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_number. 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_number 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.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue