List the logged-in user
AI agents call LIST_MY_FLIGHT_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 retrieves/queries existing flight booking data for the authenticated user. It has no side effects—it does not create, modify, delete, or execute external operations. The incomplete description ('List the logged-in user') appears truncated but the tool name clearly indicates listing flight bookings, which is a read operation.
From the tool's definition Tool name 'LIST_MY_FLIGHT_BOOKINGS' and description 'List the logged-in user' indicate retrieval of user booking data without modification.
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_FLIGHT_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_FLIGHT_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_FLIGHT_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_FLIGHT_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_FLIGHT_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 →