remove_user_from_group
AI agents call remove_user_from_group to permanently remove resources in Awslabs Valkey — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a user from a group modifies access control permissions. While technically reversible (the user can be re-added), IAM/access management changes can have immediate security and operational impact. The empty description reduces confidence, but by convention with the sibling tool 'add_user_to_group', this likely removes a user from an IAM or Valkey user group.
From the tool's definition Tool name 'remove_user_from_group' implies removing a user from a group, which is a reversible access control change. However, description is empty, lowering confidence. Sibling tool 'add_user_to_group' exists, suggesting this is the inverse operation.
Attacks that exploit this kind of access
remove_user_from_group. It is categorised as a Destructive tool in the Awslabs Valkey MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for remove_user_from_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 Awslabs Valkey. Nothing to install.
remove_user_from_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_user_from_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 remove_user_from_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.
remove_user_from_group is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.