Remove a member from a group.
AI agents call yuque_remove_group_member to permanently remove resources in Yuque Mcp Plus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a group member is a destructive operation: the membership relationship is severed, potentially revoking access to shared resources. While the member could theoretically be re-added, the action itself is not transactional or reversible in place. Given the context of a knowledge-base platform where group membership controls document access, misuse could cause significant access disruption for affected users.
From the tool's definition 'Remove a member from a group' — removing membership is an irreversible action that revokes access and cannot be undone without re-inviting the member.
Attacks that exploit this kind of access
Remove a member from a group. It is categorised as a Destructive tool in the Yuque Mcp Plus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Yuque Mcp Plus MCP server in PolicyLayer and add a rule for yuque_remove_group_member: 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 Yuque Mcp Plus. Nothing to install.
yuque_remove_group_member 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 yuque_remove_group_member 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 yuque_remove_group_member. 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.
yuque_remove_group_member is provided by the Yuque Mcp Plus MCP server (michealjou/yuque-mcp-plus). 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 →