Metadata for any theme park entity (destination, park, attraction, restaurant, or show): name, type, location, timezone, and parent ids.
AI agents call get_entity 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 | An entity id from list_destinations or get_wait_times. |
Parameters from the server's own tool schema.
This is a straightforward data retrieval tool that queries and returns structured metadata about theme park entities. It has no side effects, does not modify data, execute commands, or trigger financial operations. The blast radius of misuse is minimal—an AI could at worst retrieve excess theme park metadata, which poses no security or operational risk. Low severity is appropriate for read-only metadata access.
From the tool's definition Tool description explicitly states it retrieves metadata (name, type, location, timezone, parent ids) for theme park entities. Verbs used: 'get' and retrieves static descriptive information. No mention of creating, modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Metadata for any theme park entity (destination, park, attraction, restaurant, or show): name, type, location, timezone, and parent ids. It is categorised as a Read tool in the Mcp Themeparks MCP Server, which means it retrieves data without modifying state.
get_entity 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_entity: 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_entity 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_entity 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_entity. 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_entity 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 →