// SCAN REPORT

VoIPbin MCP Server

52 tools. 16 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

16 can modify or destroy data

36 read-only

52 tools total

Community server · catalogue entry verified 30/06/2026

How to control VoIPbin MCP Server ↓

TOOL MAP

What VoIPbin MCP Server exposes to your agents

Read (36) Write / Execute (12) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous VoIPbin MCP Server tools

Destructive · High delete_campaign The tool permanently removes a campaign from the VoIPbin platform. Destructive · High delete_conference This tool deletes a conference resource, which is an irreversible operation that eliminates data and cannot be recovered without external intervention (backups/audit logs). Destructive · High delete_contact Deletion operations cannot be undone and result in permanent data loss. Destructive · High delete_flow Deleting a flow is a destructive operation that removes configuration or automation logic irreversibly.

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

POLICY

How to control VoIPbin MCP Server

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

Deny destructive operations

{
  "delete_campaign": {
    "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_ai": {
    "limits": [
      {
        "counter": "create_ai_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_activeflow": {
    "limits": [
      {
        "counter": "get_activeflow_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 VoIPbin 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 VOIPBIN →

Instant setup, no code required.

FULL CATALOGUE

All 52 VoIPbin MCP Server tools

DESTRUCTIVE 4 tools

Destructive delete_campaign Delete a campaign. Destructive delete_conference Delete a conference. Destructive delete_contact Delete a contact. Destructive delete_flow Delete a flow.

EXECUTE 2 tools

Execute create_call create_call Execute stop_activeflow Stop a running active flow.

WRITE 10 tools

Write create_ai create_ai Write create_campaign create_campaign Write create_conference create_conference Write create_contact create_contact Write create_flow create_flow Write send_email Send an email. Write send_message Send an SMS message. Write update_campaign Update a campaign. Write update_contact Update an existing contact. Write update_flow Update an existing flow. All fields are required (full replacement).

READ 36 tools

EXPLORE

Related servers

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

FAQ

Questions about VoIPbin MCP Server

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

Yes. The VoIPbin MCP Server server exposes 4 destructive tools including delete_campaign, delete_conference, delete_contact. 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 VoIPbin MCP Server? +

The VoIPbin MCP Server server has 10 write tools including create_ai, create_campaign, create_conference. 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 VoIPbin MCP Server.

How many tools does the VoIPbin MCP Server MCP server expose? +

52 tools across 4 categories: Destructive, Execute, Read, Write. 36 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on VoIPbin MCP Server? +

Register the VoIPbin 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 VoIPbin MCP Server tool call.

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

ENFORCE POLICY ON VOIPBIN →

Instant setup, no code required.

52 VoIPbin MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.