reactivate_passenger · LumbreTravel MCP Server MCP

WHAT IT DOES

What reactivate_passenger does on LumbreTravel MCP Server

AI agents use reactivate_passenger to create or update resources in LumbreTravel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LumbreTravel MCP Server environment.

WHY IT NEEDS A POLICY

Why reactivate_passenger needs a policy

This tool changes passenger data (reactivates/restores a passenger record) in a travel management system, which is a reversible write operation. It is not destructive (data is not deleted), does not execute arbitrary code, and is not financial.

From the tool's definition Tool name 'reactivate_passenger' and description 'Reactiva un pasajero' (Reactivates a passenger) indicate a state change operation on an existing passenger record. The tool modifies passenger status reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reactivate_passenger Rate-limited

reactivate_passenger stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reactivate_passenger": {
      "limits": [
        {
          "counter": "reactivate_passenger_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LumbreTravel MCP Server, so you can run agents against it safely.

FAQ

Questions about reactivate_passenger

What does the reactivate_passenger tool do? +

Reactiva un pasajero teniendo en cuenta que se conoce su ID. It is categorised as a Write tool in the LumbreTravel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reactivate_passenger? +

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

reactivate_passenger is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reactivate_passenger? +

Yes. Add a rate_limit block to the reactivate_passenger 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 reactivate_passenger completely? +

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

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