// SCAN REPORT

3CX MCP Server

22 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

6 can modify or destroy data

16 read-only

22 tools total

Community server · catalogue entry verified 02/07/2026

How to control 3CX MCP Server ↓

TOOL MAP

What 3CX MCP Server exposes to your agents

Read (16) Write / Execute (5) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous 3CX MCP Server tools

Destructive · Critical delete_user This tool permanently and irreversibly deletes user accounts from the 3CX system. Write · Low create_department Creating a new department is a reversible write operation. Write · Medium create_user User creation is fundamentally a Write operation: it adds new data to the system in a reversible manner. Write · High set_forwarding_profile Setting a forwarding profile modifies system configuration but is not destructive in the strict sense since it can be undone by setting a different profile.

6 of 3CX MCP Server's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control 3CX MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and 3CX MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_user": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_department": {
    "limits": [
      {
        "counter": "create_department_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_contact_by_phone": {
    "limits": [
      {
        "counter": "find_contact_by_phone_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register 3CX MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON 3CX →

Instant setup, no code required.

FULL CATALOGUE

All 22 3CX MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_user [DESTRUCTIVE] Permanently deletes 3CX users by their numeric Ids. Cannot be undone. Get Ids from get_user or l

WRITE 5 tools

Write create_department [DESTRUCTIVE] Creates a new department (group) in 3CX. Returns the created department with its assigned Id. Write create_user [DESTRUCTIVE] Creates a new 3CX user/extension. The Number must be unused — use find_users first to check avai Write set_forwarding_profile [DESTRUCTIVE] Use this when the user wants to change call routing: Write update_department [DESTRUCTIVE] Updates a 3CX department by its numeric Id. Get the Id from list_departments first. Only provide Write update_user [DESTRUCTIVE] Updates a 3CX user by numeric Id. Get the Id from get_user or list_users first. Only provided fi

READ 16 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about 3CX MCP Server

Can an AI agent delete data through the 3CX MCP Server MCP server? +

Yes. The 3CX MCP Server server exposes 1 destructive tools including delete_user. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through 3CX MCP Server? +

The 3CX MCP Server server has 5 write tools including create_department, create_user, set_forwarding_profile. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach 3CX MCP Server.

How many tools does the 3CX MCP Server MCP server expose? +

22 tools across 3 categories: Destructive, Read, Write. 16 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on 3CX MCP Server? +

Register the 3CX MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every 3CX MCP Server tool call.

Deterministic rules across all 22 3CX MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON 3CX →

Instant setup, no code required.

22 3CX MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.