circles_remove_member
Remove a member from a circle/team. Use circles_list_members to get the memberId. Requires moderator privileges or higher.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/circles-remove-member.md
What circles_remove_member does on AIquila — Nextcloud MCP Server
AI agents call circles_remove_member to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
circleId | string | Yes | The circle ID to remove the member from |
memberId | string | Yes | The member ID (from circles_list_members), not the user ID |
Parameters from the server's own tool schema.
Why circles_remove_member is rated Critical
Removing a member from a circle/team is an irreversible access-control action — once removed, the member loses access to shared resources in that circle. This cannot be automatically undone and has significant blast radius if misused (e.g., removing all members or removing key members from critical teams). It falls under Destructive as it permanently removes an association.
From the tool's definition Remove a member from a circle/team
Attacks that exploit this kind of access
The rule that runs circles_remove_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For circles_remove_member, this is the rule to start with:
circles_remove_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every circles_remove_member call is checked against it from then on.
Questions about circles_remove_member
Remove a member from a circle/team. Use circles_list_members to get the memberId. Requires moderator privileges or higher. It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
circles_remove_member accepts 2 parameters: circleId, memberId. Required: circleId, memberId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for circles_remove_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 AIquila — Nextcloud MCP Server. Nothing to install.
circles_remove_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 circles_remove_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 circles_remove_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.
circles_remove_member is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
Across the catalogue