get_passengers_by_email

Obtiene pasajeros por email

Server LumbreTravel MCP Server lumile/lumbretravel-mcp
Category Read
Risk class Low
Parameters 00 required

What get_passengers_by_email does on LumbreTravel MCP Server

AI agents call get_passengers_by_email 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.

Why get_passengers_by_email needs a policy

This tool queries and retrieves passenger information filtered by email address. It performs a simple lookup with no side effects—no data is created, modified, or deleted. The operation is inherently read-only and poses minimal risk if misused, as it only exposes existing passenger records that an agent might query based on an email parameter.

From the tool's definition Tool name 'get_passengers_by_email' and description 'Obtiene pasajeros por email' (Gets passengers by email) indicate a query/retrieval operation.

Questions about get_passengers_by_email

What does the get_passengers_by_email tool do? +

Obtiene pasajeros por email. It is categorised as a Read tool in the LumbreTravel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_passengers_by_email? +

Register the LumbreTravel MCP Server MCP server in PolicyLayer and add a rule for get_passengers_by_email: 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.

What risk level is get_passengers_by_email? +

get_passengers_by_email is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_passengers_by_email? +

Yes. Add a rate_limit block to the get_passengers_by_email 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.

How do I block get_passengers_by_email completely? +

Set action: deny in the PolicyLayer policy for get_passengers_by_email. 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.

What MCP server provides get_passengers_by_email? +

get_passengers_by_email 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.