reactivate_agency · LumbreTravel MCP Server MCP

WHAT IT DOES

What reactivate_agency does on LumbreTravel MCP Server

AI agents use reactivate_agency 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_agency needs a policy

This tool modifies an agency record by changing its status from inactive to active. This is a reversible write operation—the agency state can be changed back (e.g., deactivated again). It does not permanently delete data, execute arbitrary code, move money, or trigger external operations beyond state management. The blast radius is limited to the affected agency record.

From the tool's definition Tool name 'reactivate_agency' and description 'Reactivar una agencia' (Reactivate an agency) indicate modification of an existing entity's status/state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reactivate_agency Rate-limited

reactivate_agency 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_agency": {
      "limits": [
        {
          "counter": "reactivate_agency_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_agency

What does the reactivate_agency tool do? +

Reactivar una agencia. 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_agency? +

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

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

Can I rate-limit reactivate_agency? +

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

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

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