This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-pick-from-list.md
What random_pick_from_list does on UnClick
AI agents call random_pick_from_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 |
|---|---|---|---|
count | number | — | |
items | array | Yes |
Parameters from the server's own tool schema.
Why random_pick_from_list is rated Low
This tool performs a non-destructive query operation on a list to retrieve a random element. It has no capability to modify, delete, execute external code, or trigger financial transactions.
From the tool's definition Tool name 'random_pick_from_list' and description 'Pick random item(s) from a list' indicate a retrieval operation that selects and returns data from an existing list without modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs random_pick_from_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_pick_from_list, this is the rule to start with:
random_pick_from_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_pick_from_list call is checked against it from then on.
Questions about random_pick_from_list
Pick random item(s) from a list. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
random_pick_from_list accepts 2 parameters: count, 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_pick_from_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_pick_from_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_pick_from_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_pick_from_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_pick_from_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