AI agents use add_to_cart to create or update resources in Rami Levy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rami Levy MCP Server environment.
This tool creates or modifies cart data (items and quantities) reversibly. It does not execute arbitrary code, delete data permanently, or move money. While it modifies financial-adjacent state (shopping cart), actual payment is not committed here—only the cart is prepared.
From the tool's definition The tool performs 'Add one or more items to the shopping cart' — a create/modify operation that adds data to a user's cart state, which is reversible via remove_from_cart.
Documented attack patterns abuse exactly the kind of access add_to_cart gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rami Levy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_to_cart:
{
"version": "1",
"default": "deny",
"tools": {
"add_to_cart": {
"limits": [
{
"counter": "add_to_cart_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_to_cart stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add one or more items to the shopping cart. It is categorised as a Write tool in the Rami Levy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rami Levy 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 Rami Levy 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 Rami Levy MCP Server MCP server (shilomagen/rami-levy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rami Levy MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Rami Levy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.