list-instance-tags

THE RISK

Low Risk

Why list-instance-tags needs a policy

This tool retrieves and displays existing tags associated with EC2 instances. It performs a read-only query with no ability to create, modify, delete, or execute operations. The blast radius is minimal as it only exposes metadata already associated with instances.

From the tool's definition Tool name 'list-instance-tags' and description 'List instance tags' indicate a query/retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access list-instance-tags gives an agent:

POLICY

How to control list-instance-tags

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 list-instance-tags:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list-instance-tags": {}
  }
}

list-instance-tags 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 AWS MCP Server — 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 AWS MCP Server tools

Destructive delete-ami Delete an AMI Destructive delete-bucket Delete an S3 bucket in the given region Destructive delete-db-instance Delete a given RDS DB instance in the given region Destructive delete-instance-tag Delete instance tag Destructive delete-internet-gateway Delete an internet gateway by ID in the given region Destructive delete-key-pair Delete a key pair in the given region Destructive delete-route-table Delete a route table in the given region Destructive delete-security-group Delete a security group in the given region

All 54 AWS MCP Server 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 list-instance-tags

What does the list-instance-tags tool do? +

List instance tags. It is categorised as a Read tool in the AWS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list-instance-tags? +

Register the AWS MCP Server MCP server in PolicyLayer and add a rule for list-instance-tags: 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.

What risk level is list-instance-tags? +

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

Can I rate-limit list-instance-tags? +

Yes. Add a rate_limit block to the list-instance-tags 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 list-instance-tags completely? +

Set action: deny in the PolicyLayer policy for list-instance-tags. 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 list-instance-tags? +

list-instance-tags 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.

Enforce policy on every AWS MCP Server tool call.

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.

CHECK YOUR STACK →