service_stop
Detiene y destruye una caja de servicio de flota para liberar recursos. Pasa el sandboxId devuelto por service_start. Si no se llama, la caja se auto-destruye por idle (~10 min) o al TTL.
This record as markdown: /tools/cloud-easybits-easybits/service-stop.md
What service_stop does on EasyBits
AI agents call service_stop 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 service_stop is rated Critical
Tool stops and destroys a fleet service box, an irreversible destructive action.
From the tool's definition Detiene y destruye una caja de servicio de flota para liberar recursos
Attacks that exploit this kind of access
The rule that runs service_stop 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 service_stop, this is the rule to start with:
service_stop 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 service_stop call is checked against it from then on.
Questions about service_stop
Detiene y destruye una caja de servicio de flota para liberar recursos. Pasa el sandboxId devuelto por service_start. Si no se llama, la caja se auto-destruye por idle (~10 min) o al TTL. 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 service_stop: 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.
service_stop 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 service_stop 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 service_stop. 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.
service_stop 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