This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-shuffle-list.md
What random_shuffle_list does on UnClick
AI agents call random_shuffle_list to retrieve information from UnClick 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 | array | Yes |
Parameters from the server's own tool schema.
Why random_shuffle_list is rated Low
Shuffling a list is a read-like operation: it processes input and returns output without creating, modifying, deleting, or executing anything external. The operation is reversible (the original list remains unaffected) and produces no side effects. This is a utility function with minimal risk.
From the tool's definition Tool name and description indicate it 'shuffle[s] a list randomly' — a deterministic, side-effect-free transformation of input data that returns reordered results without modifying stored state or triggering external operations.
Attacks that exploit this kind of access
The rule that runs random_shuffle_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For random_shuffle_list, this is the rule to start with:
random_shuffle_list 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 UnClick, apply this rule, and every random_shuffle_list call is checked against it from then on.
Questions about random_shuffle_list
Shuffle a list randomly. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
random_shuffle_list accepts 1 parameter: items. Required: items. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for random_shuffle_list: 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 UnClick. Nothing to install.
random_shuffle_list 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_list 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_list. 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_list is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue