Find nearby PetSmart store locations with information about available services, hours, and contact details.
AI agents call find_store to retrieve information from PetSmart MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about PetSmart store locations and their attributes. It has no capability to modify, delete, execute commands, or trigger financial transactions. The action is purely informational retrieval with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'find_store' and description indicate it retrieves store location data, available services, hours, and contact details with no modifications or side effects.
Attacks that exploit this kind of access
Find nearby PetSmart store locations with information about available services, hours, and contact details. It is categorised as a Read tool in the PetSmart MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PetSmart MCP Server MCP server in PolicyLayer and add a rule for find_store: 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 PetSmart MCP Server. Nothing to install.
find_store 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 find_store 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 find_store. 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.
find_store is provided by the PetSmart MCP Server MCP server (markswendsen-code/mcp-petsmart). 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 →