Eliminar un extra o incluído
AI agents call delete_include 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 permanently removes an included item or extra from a travel program—an action that cannot be undone. Deletion of entities qualifies as Destructive rather than Write (which is reversible). Given the travel domain context where includes/extras are likely tied to bookings or itineraries, deletion could impact multiple dependent records.
From the tool's definition Tool name 'delete_include' combined with description 'Eliminar un extra o incluído' (Spanish: Delete an extra or include). The verb 'delete' and 'eliminar' (delete) directly indicate irreversible removal of data.
Attacks that exploit this kind of access
Eliminar un extra o incluído. 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_include: 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_include 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_include 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_include. 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_include 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 →