http_dog_image
Get a dog image URL for an HTTP status code (like httpcat but with dogs).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/http-dog-image.md
What http_dog_image does on UnClick
AI agents call http_dog_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
status_code | number | Yes | HTTP status code (100-599). |
Parameters from the server's own tool schema.
Why http_dog_image is rated Low
This tool purely retrieves and returns a URL pointing to a dog image corresponding to a given HTTP status code. It is a read-only operation with no ability to modify, delete, or execute external commands. The operation has no destructive, financial, or execution consequences. Severity is low as misuse would only result in retrieving harmless image URLs.
From the tool's definition Tool name 'http_dog_image' and description 'Get a dog image URL for a HTTP status code' indicate retrieval of a static image URL resource with no side effects or data modification.
Attacks that exploit this kind of access
The rule that runs http_dog_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 http_dog_image, this is the rule to start with:
http_dog_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 http_dog_image call is checked against it from then on.
Questions about http_dog_image
Get a dog image URL for an HTTP status code (like httpcat but with dogs). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
http_dog_image accepts 1 parameter: status_code. Required: status_code. 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 http_dog_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.
http_dog_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 http_dog_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 http_dog_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.
http_dog_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