circles_remove_member

Remove a member from a circle/team. Use circles_list_members to get the memberId. Requires moderator privileges or higher.

Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Why circles_remove_member is rated Critical

Removing a member from a circle/team is an irreversible action that revokes access and membership. While technically it could be re-added, the act of removal itself is a destructive operation with significant access control implications. The requirement for 'moderator privileges or higher' underscores the sensitivity of this action.

From the tool's definition Remove a member from a circle/team

Questions about circles_remove_member

What does the circles_remove_member tool do? +

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.

How do I enforce a policy on circles_remove_member? +

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.

What risk level is circles_remove_member? +

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.

Can I rate-limit circles_remove_member? +

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.

How do I block circles_remove_member completely? +

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.

What MCP server provides circles_remove_member? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AIquila — Nextcloud MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.