list_dog_breeds
List all available dog breeds and their sub-breeds.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/list-dog-breeds.md
What list_dog_breeds does on Integrations MCP
AI agents call list_dog_breeds to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_dog_breeds is rated Low
This tool performs a simple query/list operation that retrieves information about dog breeds without modifying, executing code, deleting data, or affecting any external state. It is a standard Read operation with minimal risk.
From the tool's definition Tool name 'list_dog_breeds' and description 'List all available dog breeds and their sub-breeds' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_dog_breeds safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_dog_breeds, this is the rule to start with:
list_dog_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 Integrations MCP, apply this rule, and every list_dog_breeds call is checked against it from then on.
Questions about list_dog_breeds
List all available dog breeds and their sub-breeds. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for list_dog_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 Integrations MCP. Nothing to install.
list_dog_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 list_dog_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 list_dog_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.
list_dog_breeds is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue