AI agents invoke start_server to trigger actions in Sacloud. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Starting a server is an Execute-category action: it runs an operation whose effects depend on which server argument is provided. It is not Read (no data retrieval), Write (not reversible in the same way—starting a running server is idempotent but stopping it requires separate action), Destructive (not irreversible), Financial (not directly moving money), or Other.
From the tool's definition Tool name 'start_server' indicates it triggers an action (start) on a cloud resource (server). The tool description is empty, but context from the sibling tools (create_server, delete_bridge, attach_servers) and the server's purpose—'manage Sakura Cloud…
Documented attack patterns abuse exactly the kind of access start_server 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 start_server:
{
"version": "1",
"default": "deny",
"tools": {
"start_server": {
"limits": [
{
"counter": "start_server_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_server stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
start_server. It is categorised as a Execute tool in the Sacloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sacloud MCP server in PolicyLayer and add a rule for start_server: 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.
start_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_server 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 start_server. 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.
start_server 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.