Add a product to the PetSmart shopping cart. Optionally specify quantity and product variant (size, flavor, etc.).
AI agents use add_to_cart to create or update resources in PetSmart MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PetSmart MCP Server environment.
Adding items to a shopping cart creates or modifies data (the cart contents) without permanent destructive effects or financial commitment. It is reversible—the user can remove items or abandon the cart. This is a classic Write operation.
From the tool's definition Tool description states it 'Add[s] a product to the PetSmart shopping cart,' which modifies the user's shopping state by creating or appending items to a cart. This is reversible (items can be removed before checkout).
Attacks that exploit this kind of access
Add a product to the PetSmart shopping cart. Optionally specify quantity and product variant (size, flavor, etc.). It is categorised as a Write tool in the PetSmart MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PetSmart MCP Server MCP server in PolicyLayer and add a rule for add_to_cart: 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.
add_to_cart 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 add_to_cart 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 add_to_cart. 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.
add_to_cart 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 →