add_user_to_group
AI agents use add_user_to_group to create or update resources in AWS IoT SiteWise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS IoT SiteWise MCP Server environment.
This tool modifies user group membership, which is a reversible Write operation that changes access control state. Without a description, confidence is lowered, but the name clearly indicates user/group management. The blast radius is medium—an AI agent could incorrectly assign users to groups, granting unintended access, but this is reversible and doesn't involve data destruction or financial operations.
From the tool's definition Tool name 'add_user_to_group' indicates a membership modification action; description is empty, limiting confidence.
Attacks that exploit this kind of access
add_user_to_group. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for add_user_to_group: 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 IoT SiteWise MCP Server. Nothing to install.
add_user_to_group 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 add_user_to_group 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 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.
add_user_to_group is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.