Place the final booking order. Last step in the booking flow. BOOKING FLOW: search → get_details → get_schedule → add_to_checkout → get_checkout → create_order ━━━ TWO PAYMENT MODES ━━━ The right one depends on whether you have an API key: If you have an X-Api-Key (B2B partner integration): Use p...
Risk signalsHandles credentials or secrets (apiKey) · High parameter count (12 properties)
Part of the GetExperience server.
Free to start. No card required.
AI agents use create_order 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 create_order 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": {
"create_order": {
"limits": [
{
"counter": "create_order_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 create_order 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.
Place the final booking order. Last step in the booking flow. BOOKING FLOW: search → get_details → get_schedule → add_to_checkout → get_checkout → create_order ━━━ TWO PAYMENT MODES ━━━ The right one depends on whether you have an API key: If you have an X-Api-Key (B2B partner integration): Use paymentSystem: "internal" Booking is confirmed instantly — no card payment needed. Payment is handled outside the platform (invoicing, prepaid balance, post-payment, etc.). You must provide guest details: user object with firstName, lastName, email, tel, countryCode. Result: order confirmed, host notified, booking is active immediately. If you do NOT have an X-Api-Key (end-user booking): Use paymentSystem: "stripe" A payment link is generated — pass it to the guest to complete payment by card. You MUST provide guest details: user object with firstName, lastName, email, tel, countryCode. Result: order created with status "new" + paymentPageUrl. Share the payment link with the guest. The booking becomes active after payment. Link expires in 24 hours. NOTE: If an X-Api-Key is present but you pass "stripe", the server will automatically switch to "internal" — B2B partners always go through internal payment. ⚠️ CANCELLATION POLICY REMINDER — MANDATORY BEFORE PAYMENT: Before calling create_order, you MUST remind the user about the cancellation policy (from get_experience_details response). If the policy is strict (no refunds), explicitly warn: "Once you pay, this booking cannot be canceled or refunded." If flexible, reassure them. If unknown, advise checking with the host. Do NOT proceed to payment without this disclosure. 💰 PAYMENT TYPE CHOICE — ASK BEFORE ORDERING: Check paymentOptions from get_checkout or get_experience_details. If "part" is available, you MUST ask the user before placing the order: "Would you like to pay the full amount ($X) or just the deposit ($Y) and pay the rest on site?" Then pass the chosen paymentType ("full" or "part") to create_order. ━━━━━━━━━━━━━━━━━━━━━━━━━ [GXP_STRUCTURED] block: data.orderId, data.status, data.priceFormatted, data.paymentType, data.paidAmountFormatted, data.link, data.paymentSystem, data.paymentPageUrl, data.paymentData.. 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 create_order: 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.
create_order 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 create_order 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 create_order. 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.
create_order 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.