binotel_hangup_call
Terminate an in-progress Binotel call by generalCallID.
This record as markdown: /tools/allmcp/binotel-hangup-call.md
What binotel_hangup_call does on Allmcp
AI agents invoke binotel_hangup_call to trigger actions in Allmcp. 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 binotel_hangup_call is rated High
This tool actively terminates a live phone call, which is an external operation with real-world side effects. It does not delete data (not Destructive) nor move money (not Financial), but it executes an action on an external telephony system that cannot be undone once the call is dropped. The blast radius is high because an AI agent misusing this could disrupt active business communications.
From the tool's definition Terminate an in-progress Binotel call by generalCallID
Attacks that exploit this kind of access
The rule that runs binotel_hangup_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binotel_hangup_call, this is the rule to start with:
binotel_hangup_call 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every binotel_hangup_call call is checked against it from then on.
Questions about binotel_hangup_call
Terminate an in-progress Binotel call by generalCallID. It is categorised as a Execute tool in the Allmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the All MCP server in PolicyLayer and add a rule for binotel_hangup_call: 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 Allmcp. Nothing to install.
binotel_hangup_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the binotel_hangup_call 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.
Set action: deny in the PolicyLayer policy for binotel_hangup_call. 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.
binotel_hangup_call is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
This server
Across the catalogue