add_to_cart
AI agents use add_to_cart to create or update resources in Cz Mtg Compare — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cz Mtg Compare environment.
This tool creates or modifies a cart state (a Write action), which is reversible via 'clear_cart' or manual removal. It does not execute arbitrary code, delete data irreversibly, or commit financial transactions (no payment). The severity is medium because misuse could add unwanted items to a user's cart, potentially leading to accidental purchases, but the action is reversible before checkout.
From the tool's definition Tool name is 'add_to_cart' on an e-commerce server (MTG card price comparison with shop integration). The sibling tools include 'clear_cart', 'view_cart', and 'shop_login', confirming shopping cart functionality.
Attacks that exploit this kind of access
add_to_cart. It is categorised as a Write tool in the Cz Mtg Compare MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cz Mtg Compare 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 Cz Mtg Compare. 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 Cz Mtg Compare MCP server (xvyslo05/czech-mtg-price-comparator-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 →