AI agents invoke stop-ec2-instance to trigger actions in AWS 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.
Stopping an EC2 instance is a reversible operational action that halts a running resource but does not destroy it. While reversible (unlike Destructive actions such as terminating instances), it is an Execute-category tool because it triggers an external cloud operation with real-world effects on infrastructure. The instance and its data remain intact but become inaccessible, which could disrupt services.
From the tool's definition Tool name 'stop-ec2-instance' and description 'Stop an EC2 instance in a given region' indicate an action that triggers external operations (stopping a running compute instance) whose effects depend on arguments (region, instance ID).
Documented attack patterns abuse exactly the kind of access stop-ec2-instance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stop-ec2-instance:
{
"version": "1",
"default": "deny",
"tools": {
"stop-ec2-instance": {
"limits": [
{
"counter": "stop-ec2-instance_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop-ec2-instance 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.
Free to start. No card required.
Stop an EC2 instance in a given region. It is categorised as a Execute tool in the AWS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for stop-ec2-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 AWS MCP Server. Nothing to install.
stop-ec2-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 stop-ec2-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 stop-ec2-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.
stop-ec2-instance is provided by the AWS MCP Server MCP server (lokeswaran-aj/aws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS MCP Server, 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.
54 AWS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.