list_destinations

List all theme park destinations (Disney, Universal, Six Flags, SeaWorld, etc.) and their parks. Use this first to discover the PARK entity id, then feed that id to get_wait_times / get_schedule / get_entity.

Server Mcp Themeparks pipeworx-io/mcp-themeparks
Category Read
Risk class Low
Parameters 00 required

What list_destinations does on Mcp Themeparks

AI agents call list_destinations 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.

Why list_destinations needs a policy

This tool performs a straightforward data retrieval operation that queries an existing database of theme park destinations and returns structured reference information (entity IDs, park names, etc.). No data is created, modified, deleted, or executed as a side effect. The tool is a foundational query step for downstream operations, with no blast radius beyond exposure of publicly available theme park information.

From the tool's definition list_destinations" is described as "List all theme park destinations... Use this first to discover the PARK entity id".

Questions about list_destinations

What does the list_destinations tool do? +

List all theme park destinations (Disney, Universal, Six Flags, SeaWorld, etc.) and their parks. Use this first to discover the PARK entity id, then feed that id to get_wait_times / get_schedule / get_entity. It is categorised as a Read tool in the Mcp Themeparks MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_destinations? +

Register the Mcp Themeparks MCP server in PolicyLayer and add a rule for list_destinations: 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.

What risk level is list_destinations? +

list_destinations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_destinations? +

Yes. Add a rate_limit block to the list_destinations 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.

How do I block list_destinations completely? +

Set action: deny in the PolicyLayer policy for list_destinations. 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.

What MCP server provides list_destinations? +

list_destinations 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.