GET_MOST_TRAVELED_DESTINATIONS

Get the most-traveled-to destinations from a given origin city for a given month.

Server Travel Agent MCP Server nxgnosis/travelagentmcp
Category Read
Risk class Low
Parameters 00 required

What GET_MOST_TRAVELED_DESTINATIONS does on Travel Agent MCP Server

AI agents call GET_MOST_TRAVELED_DESTINATIONS to retrieve information from Travel Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why GET_MOST_TRAVELED_DESTINATIONS needs a policy

This tool retrieves aggregated travel statistics and destination information without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk. A misuse by an AI agent would at worst return misleading travel suggestions to a user, with no impact on data integrity, financial transactions, or system state.

From the tool's definition Tool name 'GET_MOST_TRAVELED_DESTINATIONS' and description 'Get the most-traveled-to destinations' indicate a retrieval operation with no modification of data. The verb 'Get' and absence of any mutative language confirm this is a query.

Questions about GET_MOST_TRAVELED_DESTINATIONS

What does the GET_MOST_TRAVELED_DESTINATIONS tool do? +

Get the most-traveled-to destinations from a given origin city for a given month. It is categorised as a Read tool in the Travel Agent MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on GET_MOST_TRAVELED_DESTINATIONS? +

Register the Travel Agent MCP Server MCP server in PolicyLayer and add a rule for GET_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 Agent MCP Server. Nothing to install.

What risk level is GET_MOST_TRAVELED_DESTINATIONS? +

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

Can I rate-limit GET_MOST_TRAVELED_DESTINATIONS? +

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

How do I block GET_MOST_TRAVELED_DESTINATIONS completely? +

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

What MCP server provides GET_MOST_TRAVELED_DESTINATIONS? +

GET_MOST_TRAVELED_DESTINATIONS is provided by the Travel Agent MCP Server MCP server (nxgnosis/travelagentmcp). 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.