Remove users from a group. Args: group_name: Name of the group user_ids: List of user IDs to remove Returns: Result of removing users
AI agents call remove_users_from_group to permanently remove resources in Ludus FastMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing users from a group is a destructive operation as it revokes access/membership that may not be automatically restored. While not as severe as deleting data, group membership changes can have significant access control implications and the removal is not trivially reversible without knowing the prior state. Severity is medium since it affects user permissions/access in a cyber range environment.
From the tool's definition "Remove users from a group" - removes user associations from a group
Documented attack patterns abuse exactly the kind of access remove_users_from_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_users_from_group:
{
"version": "1",
"default": "deny",
"hide": [
"remove_users_from_group"
]
}remove_users_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 users from a group. Args: group_name: Name of the group user_ids: List of user IDs to remove Returns: Result of removing users. It is categorised as a Destructive tool in the Ludus FastMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for remove_users_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 Ludus FastMCP. Nothing to install.
remove_users_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_users_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_users_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_users_from_group is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.