Eliminar un servicio
AI agents call delete_service to permanently remove resources in LumbreTravel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of a service entity within the travel management system. Deletion cannot be undone without manual intervention or backups. The high severity reflects that accidental or malicious deletion of services could disrupt travel programs and activities that depend on them.
From the tool's definition Tool name 'delete_service' combined with description 'Eliminar un servicio' (Spanish: 'Delete a service'). The verb 'delete' and 'eliminar' explicitly indicate irreversible removal of data.
Attacks that exploit this kind of access
Eliminar un servicio. It is categorised as a Destructive tool in the LumbreTravel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LumbreTravel MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_service is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →