Medium Risk

put_role_policy

Create or update an inline policy for an IAM role. This tool creates a new inline policy or updates an existing one for the specified role. Inline policies are directly embedded in a single user, role, or group and have a one-to-one relationship with the identity. Args: role_name: The name ...

Single-target operation

Part of the AWS IAM MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use put_role_policy to create or modify resources in AWS IAM MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call put_role_policy repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS IAM MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

aws-iam-mcp-server.yaml
tools:
  put_role_policy:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full AWS IAM MCP Server policy for all 29 tools.

Tool Name put_role_policy
Category Write
Risk Level Medium

View all 29 tools →

Agents calling write-class tools like put_role_policy have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the put_role_policy tool do? +

Create or update an inline policy for an IAM role. This tool creates a new inline policy or updates an existing one for the specified role. Inline policies are directly embedded in a single user, role, or group and have a one-to-one relationship with the identity. Args: role_name: The name of the IAM role policy_name: The name of the inline policy policy_document: The policy document in JSON format confirmed: Must be true to confirm this write operation Returns: InlinePolicyResponse containing the policy details and operation status. It is categorised as a Write tool in the AWS IAM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on put_role_policy? +

Add a rule in your Intercept YAML policy under the tools section for put_role_policy. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS IAM MCP Server MCP server.

What risk level is put_role_policy? +

put_role_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit put_role_policy? +

Yes. Add a rate_limit block to the put_role_policy rule in your Intercept 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 put_role_policy completely? +

Set action: deny in the Intercept 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.

What MCP server provides put_role_policy? +

put_role_policy is provided by the AWS IAM MCP Server MCP server (awslabs.iam-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.