AI agents call delete_bridge 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.
The tool name explicitly contains 'delete', which is a destructive operation that irreversibly removes a network bridge. In cloud infrastructure, deleting a bridge typically disconnects networks and cannot be easily undone without recreating the resource and its configurations.
From the tool's definition Tool name 'delete_bridge' indicates deletion of a network bridge resource in Sakura Cloud infrastructure. Sibling tools include other destructive operations (delete_router) and resource management operations (create_bridge, create_switch), confirming this is…
Documented attack patterns abuse exactly the kind of access delete_bridge 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_bridge:
{
"version": "1",
"default": "deny",
"hide": [
"delete_bridge"
]
}delete_bridge 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_bridge. 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_bridge: 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_bridge 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_bridge 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_bridge. 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_bridge 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.