dogceo.breeds.random_image
Get one or more random dog images, optionally filtered by breed and sub-breed (e.g. "hound" + "afghan"). Returns direct image URLs from the Dog CEO open-source image database. No auth required, MIT licensed.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/dogceo.breeds.random-image.md
What dogceo.breeds.random_image does on Apibase
AI agents call dogceo.breeds.random_image 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 | — | Filter by dog breed (e.g. "hound", "labrador"). Omit for a random breed. |
count | integer | — | Number of random images to return (1-50, default 1) |
sub_breed | string | — | Filter by sub-breed within the given breed (e.g. "afghan" for breed "hound"). Requires breed to also be set. |
Parameters from the server's own tool schema.
Why dogceo.breeds.random_image is rated Low
Retrieves public dog breed images without side effects or data modification.
From the tool's definition Get random dog images, returns direct image URLs from open-source database.
Attacks that exploit this kind of access
The rule that runs dogceo.breeds.random_image 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.random_image, this is the rule to start with:
dogceo.breeds.random_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 Apibase, apply this rule, and every dogceo.breeds.random_image call is checked against it from then on.
Questions about dogceo.breeds.random_image
Get one or more random dog images, optionally filtered by breed and sub-breed (e.g. "hound" + "afghan"). Returns direct image URLs from the Dog CEO open-source image database. 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.
dogceo.breeds.random_image accepts 3 parameters: breed, count, sub_breed. 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.random_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 Apibase. Nothing to install.
dogceo.breeds.random_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 dogceo.breeds.random_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 dogceo.breeds.random_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.
dogceo.breeds.random_image 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