call_destroy
Termina una videollamada limpiamente: (1) para la grabación activa si la hay y sube el MP4 a Files, (2) rescata cualquier grabación huérfana en la VM y la sube, (3) destruye el servidor. Llama esto cuando la llamada haya terminado para liberar recursos. Si no se llama, el servidor se auto-destruy...
This record as markdown: /tools/cloud-easybits-easybits/call-destroy.md
What call_destroy does on EasyBits
AI agents call call_destroy to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why call_destroy is rated Critical
Irreversibly destroys a microVM server; cannot be undone once executed.
From the tool's definition destruye el servidor, termina videollamada, liberar recursos
Attacks that exploit this kind of access
The rule that runs call_destroy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For call_destroy, this is the rule to start with:
call_destroy is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every call_destroy call is checked against it from then on.
Questions about call_destroy
Termina una videollamada limpiamente: (1) para la grabación activa si la hay y sube el MP4 a Files, (2) rescata cualquier grabación huérfana en la VM y la sube, (3) destruye el servidor. Llama esto cuando la llamada haya terminado para liberar recursos. Si no se llama, el servidor se auto-destruye al TTL (6h). It is categorised as a Destructive tool in the EasyBits MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the EasyBits MCP server in PolicyLayer and add a rule for call_destroy: 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 EasyBits. Nothing to install.
call_destroy 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 call_destroy 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 call_destroy. 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.
call_destroy is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue