This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/foodish-random.md
What foodish_random does on UnClick
AI agents call foodish_random 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 foodish_random is rated Low
This tool fetches random food images from an external API. It performs a read-only query with no ability to modify, delete, execute code, or affect financial systems. The operation is purely informational retrieval with negligible security impact if misused by an AI agent.
From the tool's definition Tool name 'foodish_random' and description 'Get a random food image from Foodish API' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs foodish_random 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 foodish_random, this is the rule to start with:
foodish_random 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 foodish_random call is checked against it from then on.
Questions about foodish_random
Get a random food image from Foodish API. 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 foodish_random: 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.
foodish_random 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 foodish_random 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 foodish_random. 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.
foodish_random 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