Get a random image URL for a specific dog breed.
AI agents call get_random_dog_by_breed to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a random dog image URL based on a breed parameter. It performs a read-only query operation against what is likely a public dog image API. There is no data creation, modification, deletion, code execution, or financial transaction involved. The only potential misuse would be excessive API calls, which would be a rate-limiting issue rather than a security risk.
From the tool's definition Tool name 'get_random_dog_by_breed' and description 'Get a random image URL for a specific dog breed' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get a random image URL for a specific dog breed. 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 get_random_dog_by_breed: 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.
get_random_dog_by_breed 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 get_random_dog_by_breed 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 get_random_dog_by_breed. 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.
get_random_dog_by_breed 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →