强制停止阿里云ECS实例(需要三次确认)
AI agents invoke power_off_alibaba_instance to trigger actions in Cloud Manage MCP Server. 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.
Powering off a cloud instance is a disruptive external operation that immediately terminates running workloads on that instance. While not permanently destructive (the instance and data persist), it causes service interruption and cannot be undone in real-time (services go down). The triple-confirmation requirement ('需要三次确认') signals the designers recognize the high blast radius.
From the tool's definition 强制停止阿里云ECS实例 (Force stop Alibaba Cloud ECS instance) — performs a power-off operation on a live cloud instance
Attacks that exploit this kind of access
强制停止阿里云ECS实例(需要三次确认). It is categorised as a Execute tool in the Cloud Manage MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cloud Manage MCP Server MCP server in PolicyLayer and add a rule for power_off_alibaba_instance: 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 Cloud Manage MCP Server. Nothing to install.
power_off_alibaba_instance 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 power_off_alibaba_instance 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 power_off_alibaba_instance. 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.
power_off_alibaba_instance is provided by the Cloud Manage MCP Server MCP server (rainhan99/cloud_manage_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →