Obtiene pasajeros por nombre completo
AI agents call get_passengers_by_fullname to retrieve information from LumbreTravel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation to retrieve passenger information based on a full name parameter. It has no side effects, does not modify data, and does not trigger external operations. It is a standard read operation consistent with the Read category for tools that retrieve or query data.
From the tool's definition Tool name 'get_passengers_by_fullname' and description 'Obtiene pasajeros por nombre completo' (Gets passengers by full name) indicate a retrieval operation that queries existing passenger data without modifying or deleting it.
Attacks that exploit this kind of access
Obtiene pasajeros por nombre completo. It is categorised as a Read tool in the LumbreTravel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LumbreTravel MCP Server MCP server in PolicyLayer and add a rule for get_passengers_by_fullname: 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 LumbreTravel MCP Server. Nothing to install.
get_passengers_by_fullname 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 get_passengers_by_fullname 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 get_passengers_by_fullname. 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.
get_passengers_by_fullname is provided by the LumbreTravel MCP Server MCP server (lumile/lumbretravel-mcp). 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 →