random_float_2
Generate random floating-point number(s).
This record as markdown: /tools/io-tinyfn-tinyfn/random-float-2.md
What random_float_2 does on TinyFn
AI agents invoke random_float_2 to trigger actions in TinyFn. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | integer | — | Number of floats to generate |
max_val | number | — | Maximum value |
min_val | number | — | Minimum value |
decimals | integer | — | Number of decimal places |
Parameters from the server's own tool schema.
Why random_float_2 is rated High
Generating random numbers is a side-effectful operation (it consumes entropy and produces non-deterministic output), distinguishing it from pure Read operations. It triggers an external operation (RNG) whose output depends on runtime state.
From the tool's definition Generate random floating-point number(s)
Attacks that exploit this kind of access
The rule that runs random_float_2 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_float_2, this is the rule to start with:
random_float_2 stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_float_2 call is checked against it from then on.
Questions about random_float_2
Generate random floating-point number(s). It is categorised as a Execute tool in the TinyFn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
random_float_2 accepts 4 parameters: count, max_val, min_val, decimals. 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_float_2: 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_float_2 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the random_float_2 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_float_2. 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_float_2 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.
Across the catalogue