AI agents use add_to_cart to create or update resources in Tuma250 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tuma250 environment.
This tool creates or modifies shopping cart data reversibly—items can be removed or modified later. It does not execute code, delete data irreversibly, or move money directly. It is a Write operation with medium severity because misuse could add unintended items to a user's cart, but the effect is reversible and financial impact requires additional user confirmation (checkout).
From the tool's definition Tool name 'add_to_cart' indicates modification of shopping cart state. Server context describes 'manage shopping carts' functionality. No description provided, but function name strongly implies cart item addition.
Attacks that exploit this kind of access
add_to_cart. It is categorised as a Write tool in the Tuma250 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tuma250 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 Tuma250. 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 Tuma250 MCP server (yann-j/tuma250_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 →