Park operating hours — opening and closing times for a theme park over the coming weeks. Pass a PARK entity_id from list_destinations.
AI agents call get_schedule to retrieve information from Mcp Themeparks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
entity_id | string | Yes | A PARK entity id from list_destinations. |
Parameters from the server's own tool schema.
This tool performs a straightforward data retrieval operation (querying theme park schedules), which is a classic Read action. It has no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal — an agent could only retrieve schedule information it shouldn't have access to, not cause operational or financial harm.
From the tool's definition Tool name 'get_schedule' and description explicitly state it retrieves 'Park operating hours — opening and closing times' with no mutation or side effects. The verb 'Pass' indicates input parameter handling, not modification.
Attacks that exploit this kind of access
Park operating hours — opening and closing times for a theme park over the coming weeks. Pass a PARK entity_id from list_destinations. It is categorised as a Read tool in the Mcp Themeparks MCP Server, which means it retrieves data without modifying state.
get_schedule accepts 1 parameter: entity_id. Required: entity_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Themeparks MCP server in PolicyLayer and add a rule for get_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 Mcp Themeparks. Nothing to install.
get_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_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_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_schedule is provided by the Mcp Themeparks MCP server (pipeworx-io/mcp-themeparks). 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 →