Get most traveled destinations from an origin
AI agents call most_traveled_destinations to retrieve information from Travel Amadeus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents historical or analytical travel data about destination popularity. It has no side effects, does not create, modify, or delete data, and does not execute code or commit financial obligations.
From the tool's definition Tool name 'most_traveled_destinations' and description 'Get most traveled destinations from an origin' indicate a query operation that retrieves aggregated travel statistics without modifying data or triggering transactional operations.
Attacks that exploit this kind of access
Get most traveled destinations from an origin. It is categorised as a Read tool in the Travel Amadeus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel Amadeus MCP Server MCP server in PolicyLayer and add a rule for most_traveled_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 Travel Amadeus MCP Server. Nothing to install.
most_traveled_destinations 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 most_traveled_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.
Set action: deny in the PolicyLayer policy for most_traveled_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.
most_traveled_destinations is provided by the Travel Amadeus MCP Server MCP server (prathush21/travel-amadeus-mcp). 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 →