Stop an EC2 instance
AI agents invoke aws_ec2_stop_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 an Execute action because it triggers an external operation (AWS API call) whose effects depend on which instance ID is provided as an argument. While reversible (unlike Destructive), it causes immediate infrastructure state changes with potential blast radius: service interruption, dependent workload failures, and operational disruption.
From the tool's definition Tool name 'aws_ec2_stop_instance' and description 'Stop an EC2 instance' indicate the tool triggers a state-changing operation on cloud infrastructure.
Attacks that exploit this kind of access
Stop an EC2 instance. 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 aws_ec2_stop_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.
aws_ec2_stop_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 aws_ec2_stop_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 aws_ec2_stop_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.
aws_ec2_stop_instance is provided by the AWS MCP Server MCP server (lokimcpuniverse/aws-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 →