remove_user_from_group
AI agents call remove_user_from_group to permanently remove resources in AWS Labs postgres MCP Server — 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 revokes their access permissions immediately. While technically it could be reversed by re-adding the user, the act of removal itself is a destructive, access-affecting operation with no undo mechanism. Given sibling tools like 'add_user_to_group' exist, this is the inverse destructive counterpart.
From the tool's definition Tool name 'remove_user_from_group' implies removal/deletion of a user-group association, which is typically irreversible without explicit re-addition.
Documented attack patterns abuse exactly the kind of access remove_user_from_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs postgres MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_user_from_group:
{
"version": "1",
"default": "deny",
"hide": [
"remove_user_from_group"
]
}remove_user_from_group disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
remove_user_from_group. It is categorised as a Destructive tool in the AWS Labs postgres MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Labs postgres MCP Server 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 AWS Labs postgres MCP Server. 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 AWS Labs postgres MCP Server MCP server (awslabs.postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs postgres MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Labs postgres MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.