random_taco
Generate a random taco recipe with base, seasoning, condiment, and shell.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-taco.md
What random_taco does on UnClick
AI agents call random_taco 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_taco is rated Low
This tool generates and returns read-only content (a random taco recipe). It has no capability to modify data, execute external commands, delete information, or commit financial transactions. The output is purely informational and deterministic based on the generate operation, making it a simple Read category tool with low severity and minimal risk if misused by an AI agent.
From the tool's definition Tool 'Generate a random taco recipe' retrieves and returns generated data (base, seasoning, condiment, shell components) with no side effects, data modification, or external operations triggered.
Attacks that exploit this kind of access
The rule that runs random_taco 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_taco, this is the rule to start with:
random_taco 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_taco call is checked against it from then on.
Questions about random_taco
Generate a random taco recipe with base, seasoning, condiment, and shell. 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_taco: 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_taco 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_taco 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_taco. 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_taco 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