Remove a user from a group membership.
AI agents call group_membership.remove to permanently remove resources in Freedcamp 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 membership is a destructive operation that revokes access and cannot be simply undone without knowing the prior state. It permanently alters the user's group associations, which could affect their permissions and access to projects/tasks within Freedcamp.
From the tool's definition 'Remove a user from a group membership' — the word 'remove' indicates an irreversible deletion of a membership relationship
Attacks that exploit this kind of access
Remove a user from a group membership. It is categorised as a Destructive tool in the Freedcamp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freedcamp MCP Server MCP server in PolicyLayer and add a rule for group_membership.remove: 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 Freedcamp MCP Server. Nothing to install.
group_membership.remove 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 group_membership.remove 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 group_membership.remove. 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.
group_membership.remove is provided by the Freedcamp MCP Server MCP server (mahrukh-n8n/freedcampmcp). 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 →