Medium Risk

add_user_to_group

Add a user to an IAM group. Args: group_name: The name of the IAM group user_name: The name of the IAM user confirmed: Must be true to confirm this write operation Returns: GroupMembershipResponse containing operation status

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

AI agents use add_user_to_group 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 add_user_to_group 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:
  add_user_to_group:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

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

Tool Name add_user_to_group
Category Write
Risk Level Medium

View all 29 tools →

Agents calling write-class tools like add_user_to_group 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 add_user_to_group tool do? +

Add a user to an IAM group. Args: group_name: The name of the IAM group user_name: The name of the IAM user confirmed: Must be true to confirm this write operation Returns: GroupMembershipResponse containing 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 add_user_to_group? +

Add a rule in your Intercept YAML policy under the tools section for add_user_to_group. 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 add_user_to_group? +

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

Can I rate-limit add_user_to_group? +

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

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

add_user_to_group 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.