List the logged-in user
AI agents call LIST_MY_HOTEL_BOOKINGS 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.
This tool queries and returns existing booking data for the authenticated user with no side effects. It is a straightforward data retrieval operation that fits the Read category. Severity is low because exposure of user's own booking list has limited blast radius, though it does reveal personal travel information.
From the tool's definition Tool name includes 'LIST' and description indicates it retrieves user booking data ('List the logged-in user'). The verb 'LIST' combined with read-only retrieval of existing booking information confirms no modification or deletion occurs.
Attacks that exploit this kind of access
List the logged-in user. It is categorised as a Read tool in the Travel Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel Agent MCP Server MCP server in PolicyLayer and add a rule for LIST_MY_HOTEL_BOOKINGS: 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.
LIST_MY_HOTEL_BOOKINGS 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 LIST_MY_HOTEL_BOOKINGS 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 LIST_MY_HOTEL_BOOKINGS. 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.
LIST_MY_HOTEL_BOOKINGS 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.
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 →