get_server_power_status
AI agents call get_server_power_status to retrieve information from Sacloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the power state of a server resource without modifying, executing commands on, or deleting infrastructure. No financial impact, irreversible changes, or code execution occurs. The description is empty, which slightly reduces confidence, but the tool name strongly indicates a straightforward status retrieval.
From the tool's definition Tool name 'get_server_power_status' indicates a read-only query operation that retrieves the current power status of a server. The verb 'get' confirms a retrieval action with no side effects.
Documented attack patterns abuse exactly the kind of access get_server_power_status 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 get_server_power_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_server_power_status": {}
}
}get_server_power_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_server_power_status. It is categorised as a Read tool in the Sacloud MCP Server, which means it retrieves data without modifying state.
Register the Sacloud MCP server in PolicyLayer and add a rule for get_server_power_status: 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.
get_server_power_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_server_power_status 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 get_server_power_status. 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.
get_server_power_status 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.