start_ecs_instances | PolicyLayer

WHAT IT DOES

What start_ecs_instances does on Alibaba Cloud Operations MCP Server

AI agents invoke start_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.

WHY IT NEEDS A POLICY

Why start_ecs_instances needs a policy

Starting ECS (Elastic Compute Service) instances is an Execute action—it runs/triggers an external operation on cloud infrastructure. While not destructive (reversible via stop_ecs_instances), it is not a read operation. The severity is high because unauthorized instance startup could incur cloud costs, disrupt services, or be used as a stepping stone for further compromise.

From the tool's definition Tool name 'start_ecs_instances' and description '启动ECS实例' (Start ECS instances) indicates execution of a state-changing operation on cloud compute resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_ecs_instances Rate-limited

start_ecs_instances 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_ecs_instances": {
      "limits": [
        {
          "counter": "start_ecs_instances_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Alibaba Cloud Operations MCP Server, so you can run agents against it safely.

FAQ

Questions about start_ecs_instances

What does the start_ecs_instances tool do? +

启动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.

How do I enforce a policy on start_ecs_instances? +

Register the Alibaba Cloud Operations MCP Server MCP server in PolicyLayer and add a rule for start_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.

What risk level is start_ecs_instances? +

start_ecs_instances is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_ecs_instances? +

Yes. Add a rate_limit block to the start_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.

How do I block start_ecs_instances completely? +

Set action: deny in the PolicyLayer policy for start_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.

What MCP server provides start_ecs_instances? +

start_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.