Xóa user khỏi group
AI agents call remove_admin_user_from_group to permanently remove resources in ServiceDesk Plus 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 permissions and group-based access. This action is not easily reversible in an automated sense (requires a separate re-add operation) and can have significant access control implications, making it Destructive with medium severity.
From the tool's definition 'Xóa user khỏi group' translates from Vietnamese to 'Remove user from group' — an irreversible removal of a user's group membership.
Attacks that exploit this kind of access
Xóa user khỏi group. It is categorised as a Destructive tool in the ServiceDesk Plus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceDesk Plus MCP Server MCP server in PolicyLayer and add a rule for remove_admin_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 ServiceDesk Plus MCP Server. Nothing to install.
remove_admin_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_admin_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_admin_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_admin_user_from_group is provided by the ServiceDesk Plus MCP Server MCP server (thichcode/servicedeskplus_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →