delete_user

[DESTRUCTIVE] Permanently deletes 3CX users by their numeric Ids. Cannot be undone. Get Ids from get_user or list_users first. Accepts an array to delete multiple users at once.

Server 3CX MCP Server ssig-it/3cx-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_user does on 3CX MCP Server

AI agents call delete_user to permanently remove resources in 3CX MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_user needs a policy

This tool permanently and irreversibly deletes user accounts from the 3CX system. There is no recovery mechanism. The ability to delete multiple users at once via array input amplifies the blast radius. An AI agent with misguided instructions could disable or remove critical business users, paralyzing phone system operations. This is the most severe category of risk.

From the tool's definition Tool description explicitly states '[DESTRUCTIVE] Permanently deletes 3CX users by their numeric Ids. Cannot be undone.' The name 'delete_user' combined with 'Permanently deletes' and 'Cannot be undone' clearly indicates irreversible data destruction.

Questions about delete_user

What does the delete_user tool do? +

[DESTRUCTIVE] Permanently deletes 3CX users by their numeric Ids. Cannot be undone. Get Ids from get_user or list_users first. Accepts an array to delete multiple users at once. It is categorised as a Destructive tool in the 3CX 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_user? +

Register the 3CX MCP Server MCP server in PolicyLayer and add a rule for delete_user: 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 3CX MCP Server. Nothing to install.

What risk level is delete_user? +

delete_user 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_user? +

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

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

delete_user is provided by the 3CX MCP Server MCP server (ssig-it/3cx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

delete_user is one line of 3CX MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.