dogceo.breeds.sub_breeds

SERVERApibase SOURCEapibase-mcp-client

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-whiteknightonhorse-apibase/dogceo.breeds.sub-breeds.md

WHAT IT DOES

What dogceo.breeds.sub_breeds does on Apibase

AI agents call dogceo.breeds.sub_breeds to retrieve information from Apibase 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	Dog breed to look up sub-breeds for (e.g. "bulldog", "terrier")

Parameters from the server's own tool schema.

RISK

Why dogceo.breeds.sub_breeds is rated Low

Retrieves dog breed data with no side effects; simple query operation.

From the tool's definition List the known sub-breeds for a single dog breed

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dogceo.breeds.sub_breeds safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dogceo.breeds.sub_breeds, this is the rule to start with:

dogceo.breeds.sub_breeds Allowed

dogceo.breeds.sub_breeds 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": {
    "dogceo.breeds.sub_breeds": {}
  }
}

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

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

FAQ

Questions about dogceo.breeds.sub_breeds

What does the dogceo.breeds.sub_breeds tool do? +

List the known sub-breeds for a single dog breed (e.g. breed="terrier" → ["american", "australian", "bedlington", ...]). Returns an empty list if the breed has no recognized sub-breeds. No auth required, MIT licensed. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does dogceo.breeds.sub_breeds accept? +

dogceo.breeds.sub_breeds 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 dogceo.breeds.sub_breeds? +

Register the Apibase MCP server in PolicyLayer and add a rule for dogceo.breeds.sub_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 Apibase. Nothing to install.

What risk level is dogceo.breeds.sub_breeds? +

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

Can I rate-limit dogceo.breeds.sub_breeds? +

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

How do I block dogceo.breeds.sub_breeds completely? +

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

What MCP server provides dogceo.breeds.sub_breeds? +

dogceo.breeds.sub_breeds is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

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