Delete a reservation. Only the owner of the reservation can delete it
AI agents call delete_reservation to permanently remove resources in Boma MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes reservation data that cannot be recovered through normal means. Although access is restricted to the reservation owner (mitigating factor), the action itself is irreversible and constitutes a destructive operation.
From the tool's definition Tool name is 'delete_reservation' and description states 'Delete a reservation.' The verb 'delete' combined with the irreversible nature of removing a reservation record makes this a destructive action.
Attacks that exploit this kind of access
Delete a reservation. Only the owner of the reservation can delete it. It is categorised as a Destructive tool in the Boma MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Boma MCP server in PolicyLayer and add a rule for delete_reservation: 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 Boma MCP. Nothing to install.
delete_reservation 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_reservation 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_reservation. 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_reservation is provided by the Boma MCP server (nicolasvegam/boma-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 →