add-to-cart
AI agents use add-to-cart to create or update resources in Terminal Shop MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Terminal Shop MCP Server environment.
Adding items to a cart creates or modifies data (the cart contents) reversibly—users can remove items later. This is a Write category action. Severity is medium because misuse could add unwanted items to a cart, but the action is reversible and lacks financial commitment until checkout.
From the tool's definition Tool named 'add-to-cart' on a shopping platform MCP server described as handling 'shopping carts' and 'place orders'. The tool modifies cart state by adding items, which is a reversible write operation.
Attacks that exploit this kind of access
add-to-cart. It is categorised as a Write tool in the Terminal Shop MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Terminal Shop 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 Terminal Shop 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 Terminal Shop MCP Server MCP server (pashaydev/terminal.shop.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 →