aws_list_ec2_instances

THE RISK

Low Risk

Why aws_list_ec2_instances needs a policy

This tool retrieves and displays information about existing EC2 instances without creating, modifying, deleting, or executing any operations on them. It is a pure query operation with no side effects, placing it squarely in the Read category. Severity is low because exposure of this data—while potentially revealing infrastructure details—does not directly enable destructive or critical actions on its own.

From the tool's definition Tool name is 'aws_list_ec2_instances' and description states 'List all EC2 instances in the current region'. The verb 'List' and the read-only nature of querying EC2 instance metadata with no modification capability.

Documented attack patterns abuse exactly the kind of access aws_list_ec2_instances gives an agent:

POLICY

How to control aws_list_ec2_instances

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Orchestrator, and nothing reaches the server without passing your rules. This is the rule we recommend for aws_list_ec2_instances:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aws_list_ec2_instances": {}
  }
}

aws_list_ec2_instances is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP Project Orchestrator — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Project Orchestrator tools

Execute orchestrate_new_project Orchestrate the setup of a new software project from the user's idea. Write deploy_skills_to_cursor Deploy Agent Skills as Cursor configuration. Write apply_project_template Apply a template and create comprehensive documentation. Write create_project_with_skills Create project using Agent Skills orchestration. Read analyze_design_patterns Analyze the user's idea to identify design patterns and architecture concepts. Read aws_best_practices Get AWS best practices for a specific service (s3, ec2, lambda) Read aws_estimate_costs Estimate AWS costs based on usage (JSON format) Read aws_list_lambda_functions List all Lambda functions in the current region

All 15 MCP Project Orchestrator tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about aws_list_ec2_instances

What does the aws_list_ec2_instances tool do? +

List all EC2 instances in the current region. It is categorised as a Read tool in the MCP Project Orchestrator MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on aws_list_ec2_instances? +

Register the MCP Project Orchestrator MCP server in PolicyLayer and add a rule for aws_list_ec2_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 MCP Project Orchestrator. Nothing to install.

What risk level is aws_list_ec2_instances? +

aws_list_ec2_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit aws_list_ec2_instances? +

Yes. Add a rate_limit block to the aws_list_ec2_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 aws_list_ec2_instances completely? +

Set action: deny in the PolicyLayer policy for aws_list_ec2_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 aws_list_ec2_instances? +

aws_list_ec2_instances is provided by the MCP Project Orchestrator MCP server (sparesparrow/mcp-project-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Project Orchestrator tool call.

Start from MCP Project Orchestrator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →