robohash_url
Generate a unique robot/monster/cat avatar from any text.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/robohash-url.md
What robohash_url does on UnClick
AI agents call robohash_url 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 |
|---|---|---|---|
bg | string | — | Background: bg1 or bg2 |
set | string | — | Style: set1 (robots), set2 (monsters), set3 (heads), set4 (cats), set5 (humans) |
size | number | — | Size in pixels (default 300) |
text | string | — | Text seed for the avatar (default robot) |
Parameters from the server's own tool schema.
Why robohash_url is rated Low
This tool generates/returns a URL or image based on input text. It is a read/fetch operation with no side effects — it constructs a deterministic avatar URL from a string. No data is written, deleted, or executed. Blast radius is minimal as misuse would only produce an avatar image.
From the tool's definition Generate a unique robot/monster/cat avatar from any text
Attacks that exploit this kind of access
The rule that runs robohash_url 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 robohash_url, this is the rule to start with:
robohash_url 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 robohash_url call is checked against it from then on.
Questions about robohash_url
Generate a unique robot/monster/cat avatar from any text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
robohash_url accepts 4 parameters: bg, set, size, 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 robohash_url: 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.
robohash_url 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 robohash_url 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 robohash_url. 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.
robohash_url 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