This record as markdown: /tools/aws/put-role-policy.md
What put_role_policy does on AWS
AI agents use put_role_policy to create or update resources in AWS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS environment.
Why put_role_policy is rated Medium
This tool modifies IAM role permissions, which is a reversible write operation that could grant unintended access to AWS resources if misconfigured by an agent. It is not destructive (policies can be removed or updated), not immediately financial, and not Execute (it configures rather than runs operations).
From the tool's definition Tool name 'put_role_policy' suggests creating or modifying an IAM role policy in AWS. Sibling tools like 'attach_group_policy' and 'attach_user_policy' are clearly policy-management operations.
Attacks that exploit this kind of access
The rule that runs put_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 put_role_policy, this is the rule to start with:
put_role_policy stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 put_role_policy call is checked against it from then on.
Questions about put_role_policy
put_role_policy is a write tool on the AWS MCP server. It is categorised as a Write tool in the AWS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS MCP server in PolicyLayer and add a rule for put_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.
put_role_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the put_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 put_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.
put_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