AI agents call get_role_policy to retrieve information from AWS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to fetch or query IAM role policy data based on its name. Without a description, confidence is moderate. The semantic pattern of 'get_' operations in AWS contexts typically indicates read-only retrieval. Even if misused by an agent, retrieving policy information does not modify systems or cause blast radius beyond information disclosure. Severity is low because this is reconnaissance-level access.
From the tool's definition Tool name 'get_role_policy' indicates retrieval of role policy information. Description is empty, but the 'get_' prefix and the lack of mutation keywords (create, delete, update, attach, detach) are consistent with a read operation.
Documented attack patterns abuse exactly the kind of access get_role_policy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for get_role_policy:
{
"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.
Free to start. No card required.
get_role_policy. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS 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 AWS. Nothing to install.
get_role_policy is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_role_policy is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS, 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.
300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.