This record as markdown: /tools/aws/get-role-policy.md
What get_role_policy does on AWS
AI agents call get_role_policy to retrieve information from AWS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_role_policy is rated Low
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.
Attacks that exploit this kind of access
The rule that runs get_role_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_role_policy, this is the rule to start with:
get_role_policy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every get_role_policy call is checked against it from then on.
Questions about get_role_policy
get_role_policy is a read tool on the AWS MCP server. 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.
More on AWS, and thousands of servers like it.
This server
Across the catalogue