filter_hotels_by_amenities
AI agents call filter_hotels_by_amenities to retrieve information from MCP Travel Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to search or filter existing hotel data based on amenity criteria, which is a read operation with no side effects. No data is created, modified, deleted, or financial transactions occur. Empty description lowers confidence slightly, but the naming pattern and server context (travel planning) clearly indicate a read-only query tool.
From the tool's definition Tool name 'filter_hotels_by_amenities' indicates a filtering/querying operation. The description is empty, but context from sibling tools (all read-only filters: filter_events_by_*, filter_flights_by_*) and the 'filter_' prefix strongly suggest this retrieves…
Attacks that exploit this kind of access
filter_hotels_by_amenities. It is categorised as a Read tool in the MCP Travel Planner MCP Server, which means it retrieves data without modifying state.
Register the MCP Travel Planner MCP server in PolicyLayer and add a rule for filter_hotels_by_amenities: 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 Travel Planner. Nothing to install.
filter_hotels_by_amenities 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 filter_hotels_by_amenities 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 filter_hotels_by_amenities. 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.
filter_hotels_by_amenities is provided by the MCP Travel Planner MCP server (leonavevor/mcp_travelassistant). 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 →