Add an experience to the cart. Call get_experience_schedule first and take configId, startAt from the chosen slot — pass them here EXACTLY as returned. Also pass durationMinutes when the slot provides it; if it is null, you may omit it and the server will substitute the experience's default durat...
Risk signalsHigh parameter count (12 properties)
Part of the GetExperience server.
Free to start. No card required.
AI agents use add_to_checkout to create or modify resources in GetExperience. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call add_to_checkout repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach GetExperience.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"add_to_checkout": {
"limits": [
{
"counter": "add_to_checkout_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full GetExperience policy for all 6 tools.
These attack patterns abuse exactly the kind of access add_to_checkout gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Add an experience to the cart. Call get_experience_schedule first and take configId, startAt from the chosen slot — pass them here EXACTLY as returned. Also pass durationMinutes when the slot provides it; if it is null, you may omit it and the server will substitute the experience's default duration. RETURNS: sessionId, checkoutId, total price. ⚠️ SAVE sessionId — you will need it for get_checkout and create_order. To add multiple experiences to the same cart: reuse the same sessionId in subsequent calls. NEXT STEP: After adding to cart, call get_checkout to see full cart details including payment options. If partial payment is available, the checkout will show deposit amount vs total — present both to the user. BOOKING FLOW: get_experience_schedule → add_to_checkout → get_checkout → create_order [GXP_STRUCTURED] block: data.sessionId, data.checkoutId, data.totalPriceFormatted.. It is categorised as a Write tool in the GetExperience MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GetExperience MCP server in PolicyLayer and add a rule for add_to_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.
add_to_checkout 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_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 add_to_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.
add_to_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.