在ECS实例上运行命令
AI agents invoke run_ecs_command 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 code/commands on ECS (Elastic Compute Service) instances, which is a core Execute category action. The blast radius is high because commands run on production infrastructure can cause availability issues, data access, or lateral movement.
From the tool's definition Tool name 'run_ecs_command' and description '在ECS实例上运行命令' (run command on ECS instance) directly indicate execution of arbitrary commands on cloud compute 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 run_ecs_command: 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.
run_ecs_command 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 run_ecs_command 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 run_ecs_command. 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.
run_ecs_command 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 →