cataas_random_cat
Get a random cat image, optionally with a tag or text overlay.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cataas-random-cat.md
What cataas_random_cat does on UnClick
AI agents call cataas_random_cat 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 |
|---|---|---|---|
tag | string | — | Filter by tag (e.g. cute, funny, sleeping) |
text | string | — | Text to overlay on the image |
Parameters from the server's own tool schema.
Why cataas_random_cat is rated Low
This tool queries and returns data (a cat image) without creating, modifying, deleting, or executing anything. It is purely informational retrieval, making it a Read category risk with low severity.
From the tool's definition Tool description states 'Get a random cat image' — a retrieval operation with no side effects. The optional parameters (tag, text overlay) are for filtering/formatting the response, not modifying server state.
Attacks that exploit this kind of access
The rule that runs cataas_random_cat 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 cataas_random_cat, this is the rule to start with:
cataas_random_cat 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 cataas_random_cat call is checked against it from then on.
Questions about cataas_random_cat
Get a random cat image, optionally with a tag or text overlay. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cataas_random_cat accepts 2 parameters: tag, text. 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 cataas_random_cat: 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.
cataas_random_cat 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 cataas_random_cat 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 cataas_random_cat. 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.
cataas_random_cat 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