dog_api_breeds
List dog breeds with details from The Dog API.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/dog-api-breeds.md
What dog_api_breeds does on UnClick
AI agents call dog_api_breeds 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 |
|---|---|---|---|
page | number | — | Page number (default 0) |
limit | number | — | Number of breeds to return (max 50, default 20) |
Parameters from the server's own tool schema.
Why dog_api_breeds is rated Low
The dog_api_breeds tool performs a read-only lookup against The Dog API. It retrieves public breed information and returns it to the caller with no side effects, data modification, or external state changes. This is a straightforward informational query with minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'List dog breeds with details from The Dog API' — this is a retrieval operation that queries and returns breed data without modifying any state.
Attacks that exploit this kind of access
The rule that runs dog_api_breeds 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 dog_api_breeds, this is the rule to start with:
dog_api_breeds 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 dog_api_breeds call is checked against it from then on.
Questions about dog_api_breeds
List dog breeds with details from The Dog API. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
dog_api_breeds accepts 2 parameters: page, limit. 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 dog_api_breeds: 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.
dog_api_breeds 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 dog_api_breeds 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 dog_api_breeds. 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.
dog_api_breeds 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