delete_account

Delete an account from a project. Requires the ETag for optimistic concurrency control.

Server TreeBeam MCP Server treebeam-code/tb-mcpserver
Category Destructive
Risk class Critical
Parameters 00 required

What delete_account does on TreeBeam MCP Server

AI agents call delete_account 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.

Why delete_account needs a policy

Deleting an account from a financial management/accounting platform is an irreversible operation that removes data and cannot be undone. This falls under Destructive category (most severe applicable). Severity is high because deletion of financial accounts could cause significant business impact, though not as critical as cascading multi-account deletion or system-wide destructive operations.

From the tool's definition Tool name is 'delete_account' and description states 'Delete an account from a project.' The verb 'Delete' combined with irreversible removal of a financial account constitutes a destructive action.

Questions about delete_account

What does the delete_account tool do? +

Delete an account from a project. Requires the 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.

How do I enforce a policy on delete_account? +

Register the TreeBeam MCP Server MCP server in PolicyLayer and add a rule for delete_account: 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.

What risk level is delete_account? +

delete_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_account? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.