Get current cart contents by sessionId. Use when: you need to confirm what's in the cart before placing the order, or to retrieve checkoutId if it was not saved after add_to_checkout. sessionId is returned by add_to_checkout — always save it. RETURNS: checkoutId (required for create_order), list ...
Part of the GetExperience server.
Free to start. No card required.
AI agents call get_checkout to retrieve information from GetExperience without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_checkout only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_checkout": {}
}
}See the full GetExperience policy for all 6 tools.
These attack patterns abuse exactly the kind of access get_checkout gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get current cart contents by sessionId. Use when: you need to confirm what's in the cart before placing the order, or to retrieve checkoutId if it was not saved after add_to_checkout. sessionId is returned by add_to_checkout — always save it. RETURNS: checkoutId (required for create_order), list of items with titles and prices, total price, payment options. 💰 PARTIAL PAYMENT INFO: If paymentOptions includes "part", the response shows: - Total price (full amount) - Pay now (deposit amount) - Pay on site (remaining amount) Present all three amounts to the user clearly. Before proceeding to create_order, ask: "Would you like to pay the full amount or just the deposit?" [GXP_STRUCTURED] block: data.checkoutId, data.items[], data.totalPriceFormatted, data.paymentOptions, data.totalPrepayPriceFormatted, data.payLaterPriceFormatted.. It is categorised as a Read tool in the GetExperience MCP Server, which means it retrieves data without modifying state.
Register the GetExperience MCP server in PolicyLayer and add a rule for get_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 GetExperience. Nothing to install.
get_checkout is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_checkout is provided by the GetExperience MCP server (https://getexperience.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 GetExperience tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.