AI agents call delete_router to permanently remove resources in Sacloud — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a router is an irreversible action that destroys cloud infrastructure and cannot be undone. This falls squarely into the Destructive category. The high severity reflects that router deletion could disrupt network connectivity for dependent services. The confidence is 0.95 rather than 1.0 because the description is empty; however, the tool name unambiguously indicates a destructive operation.
From the tool's definition Tool name is 'delete_router' with no description provided. The verb 'delete' combined with 'router' (a core network infrastructure component in Sakura Cloud) indicates irreversible removal of a networking resource.
Documented attack patterns abuse exactly the kind of access delete_router gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sacloud, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_router:
{
"version": "1",
"default": "deny",
"hide": [
"delete_router"
]
}delete_router disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_router. It is categorised as a Destructive tool in the Sacloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sacloud MCP server in PolicyLayer and add a rule for delete_router: 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 Sacloud. Nothing to install.
delete_router 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_router 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_router. 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_router is provided by the Sacloud MCP server (sacloud/sacloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sacloud, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Sacloud tools catalogued and risk-classified — across an index of 43,000+ MCP servers.