reactivate_service_language · LumbreTravel MCP Server MCP

WHAT IT DOES

What reactivate_service_language does on LumbreTravel MCP Server

AI agents use reactivate_service_language 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_service_language needs a policy

This tool modifies data reversibly by reactivating (changing state of) a service language. It is not destructive since reactivation can be undone by deactivating again. It does not execute arbitrary code or commands, nor does it involve financial transactions. The modification affects travel service language settings, which could impact service availability if misused, warranting medium severity.

From the tool's definition Tool name 'reactivate_service_language' and description 'Reactivar un idioma de servicio' (Reactivate a service language) indicates a state change operation that modifies an existing service language entity from inactive to active status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reactivate_service_language Rate-limited

reactivate_service_language 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_service_language": {
      "limits": [
        {
          "counter": "reactivate_service_language_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_service_language

What does the reactivate_service_language tool do? +

Reactivar un idioma de servicio. 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_service_language? +

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

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

Can I rate-limit reactivate_service_language? +

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

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

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