AI agents call random_bytes 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 |
|---|---|---|---|
length | integer | — | Number of bytes |
encoding | string | — | Output encoding: hex, base64 |
Parameters from the server's own tool schema.
This tool generates random data for use (e.g., cryptographic keys, tokens, nonces) but does not retrieve, modify, or delete persistent state. It is a pure generator with no blast radius if misused—the worst outcome is using weak randomness for a particular cryptographic purpose, but the tool itself performs no destructive or external operations.
From the tool's definition Tool name 'random_bytes' and description 'Generate cryptographically secure random bytes' indicate data generation with no side effects, no modifications to existing data, and no execution of external operations.
Attacks that exploit this kind of access
Generate cryptographically secure random bytes. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_bytes accepts 2 parameters: length, encoding. 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_bytes: 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_bytes 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_bytes 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_bytes. 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_bytes 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_bytes 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 →