dogceo.breeds.list
List every dog breed in the Dog CEO database, each with its known sub-breeds (e.g. "bulldog" → ["boston", "english", "french"]). Set include_sub_breeds=false for a flat list of breed names only. No auth required, MIT licensed.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/dogceo.breeds.list.md
What dogceo.breeds.list does on Apibase
AI agents use dogceo.breeds.list to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
include_sub_breeds | boolean | — | Include the nested sub-breeds array for each breed (default true). Set false for a flat list of breed names only. |
Parameters from the server's own tool schema.
Why dogceo.breeds.list is rated Medium
An AI agent can call dogceo.breeds.list faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs dogceo.breeds.list 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.list, this is the rule to start with:
dogceo.breeds.list stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every dogceo.breeds.list call is checked against it from then on.
Questions about dogceo.breeds.list
List every dog breed in the Dog CEO database, each with its known sub-breeds (e.g. "bulldog" → ["boston", "english", "french"]). Set include_sub_breeds=false for a flat list of breed names only. No auth required, MIT licensed. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dogceo.breeds.list accepts 1 parameter: include_sub_breeds. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for dogceo.breeds.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 Apibase. Nothing to install.
dogceo.breeds.list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dogceo.breeds.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.
Set action: deny in the PolicyLayer policy for dogceo.breeds.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.
dogceo.breeds.list 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue