Remove a contact from a group.
AI agents call remove_from_group to permanently remove resources in Nexus Core — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a contact from a group is a destructive action — the membership association is deleted. While the contact itself is not deleted, the group membership removal may not be easily reversible (especially if audit history is not maintained), making it qualify as Destructive rather than just Write. Misuse could silently remove contacts from important groups, disrupting communications or access.
From the tool's definition Remove a contact from a group
Attacks that exploit this kind of access
Remove a contact from a group. It is categorised as a Destructive tool in the Nexus Core MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nexus Core MCP server in PolicyLayer and add a rule for remove_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 Nexus Core. Nothing to install.
remove_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_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_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_from_group is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →