search_hotels
A read tool on the A2a Multi Agent Travel MCP server.
This record as markdown: /tools/a2a-multi-agent-travel/search-hotels.md
What search_hotels does on A2a Multi Agent Travel
AI agents call search_hotels to retrieve information from A2a Multi Agent Travel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_hotels is rated Low
This tool retrieves or queries hotel data without creating, modifying, or deleting anything. It fits the Read category pattern of search/query operations with no side effects. Severity is low because misuse would only expose travel information, not cause financial transactions, data loss, or system compromise.
From the tool's definition Tool name is 'search_hotels' and server description indicates it 'search hotels' among travel services. No description provided for the tool itself, but the naming convention and context strongly suggest a read-only search operation.
Attacks that exploit this kind of access
The rule that runs search_hotels safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A2a Multi Agent Travel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_hotels, this is the rule to start with:
search_hotels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect A2a Multi Agent Travel, apply this rule, and every search_hotels call is checked against it from then on.
Questions about search_hotels
search_hotels is a read tool on the A2a Multi Agent Travel MCP server. It is categorised as a Read tool in the A2a Multi Agent Travel MCP Server, which means it retrieves data without modifying state.
Register the A2a Multi Agent Travel MCP server in PolicyLayer and add a rule for search_hotels: 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 A2a Multi Agent Travel. Nothing to install.
search_hotels 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 search_hotels 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 search_hotels. 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.
search_hotels is provided by the A2a Multi Agent Travel MCP server (fnusatvik07/a2a-multi-agent-travel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A2a Multi Agent Travel, and thousands of servers like it.
This server
Across the catalogue