Get available time slots for a specific experience on a specific date. Required step before booking. CRITICAL: Copy configId and startAt EXACTLY from the chosen slot — pass these unchanged to add_to_checkout. Do not modify or recalculate these values. Copy durationMinutes when the slot provides i...
Part of the GetExperience server.
Free to start. No card required.
AI agents call get_experience_schedule 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_experience_schedule 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_experience_schedule": {}
}
}See the full GetExperience policy for all 6 tools.
These attack patterns abuse exactly the kind of access get_experience_schedule 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 available time slots for a specific experience on a specific date. Required step before booking. CRITICAL: Copy configId and startAt EXACTLY from the chosen slot — pass these unchanged to add_to_checkout. Do not modify or recalculate these values. Copy durationMinutes when the slot provides it; if the slot returns durationMinutes as null (common for on-demand or flexible schedules), you may omit it from add_to_checkout — the server will fill it in from the experience's default duration. All prices are in USD. RETURNS: available slots with configId, startAt (ISO datetime), durationMinutes. Each slot exposes price per adult / child / private group in two formats: - numeric USD values: priceAdult, priceChild, pricePrivateGroup (for arithmetic — e.g. priceAdult * adults) - formatted display strings: priceAdultFormatted, priceChildFormatted, pricePrivateGroupFormatted (e.g. "US$45.00", for display) BOOKING FLOW: search_experiences → get_experience_schedule → add_to_checkout → create_order [GXP_STRUCTURED] block: data.slots[] — array of available slots with all pricing details.. 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_experience_schedule: 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_experience_schedule 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_experience_schedule 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_experience_schedule. 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_experience_schedule 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.