Add a menu item to the cart with optional customizations.
AI agents use add_to_cart to create or update resources in Burger King MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Burger King MCP Server environment.
This tool modifies cart state by adding items, which is a reversible Write operation. While the broader ordering system could facilitate financial transactions (via the checkout sibling tool), add_to_cart itself only stages items for purchase without committing funds.
From the tool's definition Tool description states 'Add a menu item to the cart' - this creates/modifies cart data. The server description mentions 'manage a cart with item customizations', confirming reversible state changes.
Attacks that exploit this kind of access
Add a menu item to the cart with optional customizations. It is categorised as a Write tool in the Burger King MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Burger King 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 Burger King 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 Burger King MCP Server MCP server (markswendsen-code/mcp-burgerking). 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 →