update_service · LumbreTravel MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_service does on LumbreTravel MCP Server

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

This tool modifies existing service data within the LumbreTravel system. It is a Write operation because it creates or modifies data reversibly without irreversibly deleting information. Severity is medium because unauthorized updates to travel services could disrupt bookings or service availability, but the action is reversible and does not directly involve financial transactions or destructive deletion.

From the tool's definition Tool name is 'update_service' and description states 'Actualizar un servicio' (Update a service). The 'update' verb and the context of a travel management system indicate data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_service Rate-limited

update_service 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": {
    "update_service": {
      "limits": [
        {
          "counter": "update_service_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 update_service

What does the update_service tool do? +

Actualizar un 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 update_service? +

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

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

Can I rate-limit update_service? +

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

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

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