停止ECS实例
AI agents invoke stop_ecs_instances to trigger actions in Alibaba Cloud Operations 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.
This tool executes a command to stop running cloud compute instances, which is a state-changing operation with side effects on live infrastructure. It is reversible (instances can be restarted), so it does not qualify as Destructive. However, stopping production instances can disrupt services and operations, making it an Execute-category risk.
From the tool's definition Tool name is 'stop_ecs_instances' and description indicates stopping ECS (Elastic Compute Service) instances.
Attacks that exploit this kind of access
停止ECS实例. It is categorised as a Execute tool in the Alibaba Cloud Operations MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Alibaba Cloud Operations MCP Server MCP server in PolicyLayer and add a rule for stop_ecs_instances: 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 Alibaba Cloud Operations MCP Server. Nothing to install.
stop_ecs_instances 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 stop_ecs_instances 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 stop_ecs_instances. 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.
stop_ecs_instances is provided by the Alibaba Cloud Operations MCP Server MCP server (radiumgu/alicloud-ops-mcp). 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 →