Complete the purchase process for items in the PetSmart shopping cart. Fills in shipping information to initiate checkout.
AI agents use checkout to commit financial operations through PetSmart MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Checkout commits a financial obligation by completing a purchase. This directly involves spending money, making it Financial category. The blast radius is critical because an AI agent misusing this tool could make unauthorized purchases on behalf of the user.
From the tool's definition 'Complete the purchase process' and 'initiate checkout' — this tool finalizes a financial transaction by processing payment for items in the cart.
Attacks that exploit this kind of access
Complete the purchase process for items in the PetSmart shopping cart. Fills in shipping information to initiate checkout. It is categorised as a Financial tool in the PetSmart MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the PetSmart MCP Server MCP server in PolicyLayer and add a rule for checkout: 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.
checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the checkout 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 checkout. 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.
checkout 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 →