dog_breed_list

List sub-breeds of a specific dog breed.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/dog-breed-list.md

WHAT IT DOES

What dog_breed_list does on UnClick

AI agents call dog_breed_list 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
`breed`	string	Yes	Breed name (e.g. bulldog, hound)

Parameters from the server's own tool schema.

RISK

Why dog_breed_list is rated Low

This tool queries and returns information about dog breed classifications. It performs a simple lookup/list operation with no capability to modify, delete, or execute arbitrary operations. The blast radius of misuse is negligible—returning incorrect breed information poses no security, financial, or operational risk.

From the tool's definition Tool name 'dog_breed_list' and description 'List sub-breeds of a specific dog breed' indicate a retrieval operation with no data modification, deletion, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dog_breed_list 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_breed_list, this is the rule to start with:

dog_breed_list Allowed

dog_breed_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dog_breed_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every dog_breed_list call is checked against it from then on.

FAQ

Questions about dog_breed_list

What does the dog_breed_list tool do? +

List sub-breeds of a specific dog breed. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does dog_breed_list accept? +

dog_breed_list accepts 1 parameter: breed. Required: breed. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dog_breed_list? +

Register the UnClick MCP server in PolicyLayer and add a rule for dog_breed_list: 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.

What risk level is dog_breed_list? +

dog_breed_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dog_breed_list? +

Yes. Add a rate_limit block to the dog_breed_list 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.

How do I block dog_breed_list completely? +

Set action: deny in the PolicyLayer policy for dog_breed_list. 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.

What MCP server provides dog_breed_list? +

dog_breed_list 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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →