This record as markdown: /tools/io-tinyfn-tinyfn/random-shuffle.md
What random_shuffle does on TinyFn
AI agents call random_shuffle 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 |
|---|---|---|---|
items | string | Yes | Comma-separated items to shuffle |
Parameters from the server's own tool schema.
Why random_shuffle is rated Low
This tool takes a list as input and returns a shuffled version. It is a pure, deterministic-style transformation (despite using randomness) with no external side effects, no data modification, and no destructive actions. It fits best under Read as it simply processes and returns data without persisting or altering anything outside its scope.
From the tool's definition Randomly shuffle a list of items — operates on input data and returns a reordered list with no side effects, no external calls, and no persistent state changes.
Attacks that exploit this kind of access
The rule that runs random_shuffle 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_shuffle, this is the rule to start with:
random_shuffle 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_shuffle call is checked against it from then on.
Questions about random_shuffle
Randomly shuffle a list of items. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_shuffle accepts 1 parameter: items. Required: items. 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_shuffle: 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_shuffle 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_shuffle 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_shuffle. 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_shuffle 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