This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-duck-image.md
What random_duck_image does on UnClick
AI agents call random_duck_image 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_image is rated Low
This tool retrieves and returns a duck image URL with no side effects. It is purely informational and read-only, matching the 'Read' category definition of data retrieval without side effects. The narrow, deterministic scope (returning a random image URL) and lack of any modifiable state makes this a trivial low-severity case.
From the tool's definition Tool name and description explicitly indicate a retrieval operation: 'Get a random duck image URL.' No parameters are mentioned that would allow side effects, data modification, deletion, or external system manipulation.
Attacks that exploit this kind of access
The rule that runs random_duck_image 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_image, this is the rule to start with:
random_duck_image 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_image call is checked against it from then on.
Questions about random_duck_image
Get a random duck image URL. 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_image: 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_image 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_image 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_image. 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_image 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