Delete an entity from a project. Requires the entity ETag for optimistic concurrency control.
AI agents call delete_entity to permanently remove resources in TreeBeam MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data from a financial management and accounting platform. In a financial context, deleting entities (accounts, transactions, or other ledger items) is destructive and cannot be undone. An AI agent misusing this could permanently erase critical financial records. This is more severe than Write operations and falls squarely into the Destructive category.
From the tool's definition Tool name 'delete_entity' combined with description 'Delete an entity from a project' explicitly indicates irreversible deletion.
Attacks that exploit this kind of access
Delete an entity from a project. Requires the entity ETag for optimistic concurrency control. It is categorised as a Destructive tool in the TreeBeam MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TreeBeam MCP Server MCP server in PolicyLayer and add a rule for delete_entity: 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 TreeBeam MCP Server. Nothing to install.
delete_entity 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_entity 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_entity. 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_entity is provided by the TreeBeam MCP Server MCP server (treebeam-code/tb-mcpserver). 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 →