This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-duck-list.md
What random_duck_list does on UnClick
AI agents call random_duck_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.
Why random_duck_list is rated Low
This tool queries and returns a static list of filenames—a pure read operation with no capability to modify, delete, or execute anything. The filename list is informational only and poses minimal security risk if misused by an AI agent.
From the tool's definition Tool name 'random_duck_list' and description 'List all available duck image filenames' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs random_duck_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_duck_list, this is the rule to start with:
random_duck_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_duck_list call is checked against it from then on.
Questions about random_duck_list
List all available duck image filenames. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for random_duck_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_duck_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_duck_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_duck_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_duck_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