Delete a flow.
AI agents call delete_flow to permanently remove resources in VoIPbin MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a flow is a destructive operation that removes configuration or automation logic irreversibly. In a VoIPbin CPaaS platform context, flows typically represent call routing, IVR logic, or messaging workflows. Deletion cannot be undone without manual restoration or backups, making this a Destructive category action.
From the tool's definition Tool name: 'delete_flow'. Tool description: 'Delete a flow.' The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a flow. It is categorised as a Destructive tool in the VoIPbin MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the VoIPbin MCP Server MCP server in PolicyLayer and add a rule for delete_flow: 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.
delete_flow is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_flow 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 delete_flow. 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.
delete_flow 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →