Low Risk

get_role_policy

get_role_policy

How to control get_role_policy ↓

What get_role_policy does on Amazon ECS MCP Server

AI agents call get_role_policy to retrieve information from Amazon ECS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_role_policy needs a policy

The 'get' prefix strongly suggests this tool retrieves or queries IAM role policy information without modification. The empty description prevents higher confidence, but naming conventions and the presence of other policy-related tools in the sibling list (add_inline_policy) that perform writes support this classification as a read operation.

From the tool's definition Tool name 'get_role_policy' indicates a retrieval operation following AWS IAM API conventions where 'get' operations are read-only queries.

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

How to control get_role_policy

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_role_policy": {}
  }
}

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

  1. Create a free account and register Amazon ECS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_role_policy

What does the get_role_policy tool do? +

get_role_policy. It is categorised as a Read tool in the Amazon ECS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_role_policy? +

Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for get_role_policy: 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 Amazon ECS MCP Server. Nothing to install.

What risk level is get_role_policy? +

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

Can I rate-limit get_role_policy? +

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

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

get_role_policy is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon ECS MCP Server tool call.

Start from Amazon ECS 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.

805 Amazon ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.