reactivate_leader · LumbreTravel MCP Server MCP

WHAT IT DOES

What reactivate_leader does on LumbreTravel MCP Server

AI agents use reactivate_leader 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_leader needs a policy

This tool creates or modifies data reversibly. Reactivating a leader changes their account status but does not delete data and the action can be undone (by deactivating again). It falls under Write category rather than Execute, as it performs a specific data state change rather than executing arbitrary code.

From the tool's definition Tool name is 'reactivate_leader' and description states 'Reactivar un guía' (Reactivate a guide). This modifies the state of an existing leader/guide entity by changing their status from inactive to active.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reactivate_leader Rate-limited

reactivate_leader 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_leader": {
      "limits": [
        {
          "counter": "reactivate_leader_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_leader

What does the reactivate_leader tool do? +

Reactivar un guía. 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_leader? +

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

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

Can I rate-limit reactivate_leader? +

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

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

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