stop_activeflow · VoIPbin MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_activeflow does on VoIPbin MCP Server

AI agents invoke stop_activeflow to trigger actions in VoIPbin MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why stop_activeflow needs a policy

This tool triggers an external operation (stopping a flow) whose effects depend on which flow is targeted. It is not merely reading data (Read), nor is it creating/modifying data reversibly (Write). It is not permanently destructive (Destructive), as flows can typically be restarted. The operation executes a command on the platform infrastructure, making it Execute-category.

From the tool's definition Tool name 'stop_activeflow' and description 'Stop a running active flow' indicate execution of an operation that terminates an active process on the VoIPbin CPaaS platform. The action interrupts running communication/workflow operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_activeflow Rate-limited

stop_activeflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_activeflow": {
      "limits": [
        {
          "counter": "stop_activeflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches VoIPbin MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_activeflow

What does the stop_activeflow tool do? +

Stop a running active flow. It is categorised as a Execute tool in the VoIPbin MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_activeflow? +

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

What risk level is stop_activeflow? +

stop_activeflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_activeflow? +

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

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

stop_activeflow is provided by the VoIPbin MCP Server MCP server (voipbin/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.