This record as markdown: /tools/io-tinyfn-tinyfn/random-element.md
What random_element does on TinyFn
AI agents call random_element 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 | — | Number of elements to pick |
Parameters from the server's own tool schema.
Why random_element is rated Low
This tool retrieves random data from a deterministic set (chemical elements) without modifying, executing code, deleting resources, or moving funds. It is a pure read operation with no side effects. Severity is low because misuse cannot cause harm—returning incorrect or repeated chemical elements poses minimal risk to any system.
From the tool's definition Tool description states 'Get random chemical element(s)' — a retrieval operation with no parameters that affect external state or data persistence. It returns information only.
Attacks that exploit this kind of access
The rule that runs random_element 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_element, this is the rule to start with:
random_element 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_element call is checked against it from then on.
Questions about random_element
Get random chemical element(s). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_element accepts 1 parameter: count. 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_element: 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_element 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_element 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_element. 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_element 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