Proceed to checkout with the current cart. Initiates the order on bk.com via browser automation.
AI agents use checkout to commit financial operations through Burger King MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a real financial transaction by placing an order on Burger King's website. It commits a financial obligation (food purchase) on behalf of the user via browser automation. Misuse could result in unauthorized orders being placed and charged to the user's payment method, making it Financial category with critical severity.
From the tool's definition 'Proceed to checkout with the current cart. Initiates the order on bk.com via browser automation.'
Attacks that exploit this kind of access
Proceed to checkout with the current cart. Initiates the order on bk.com via browser automation. It is categorised as a Financial tool in the Burger King MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Burger King MCP Server MCP server in PolicyLayer and add a rule for checkout: 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.
checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the checkout 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 checkout. 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.
checkout 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 →