remove_user_from_group

Remove a Nextcloud user from a group. Requires admin privileges

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/remove-user-from-group.md

What remove_user_from_group does on AIquila — Nextcloud MCP Server

AI agents call remove_user_from_group 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 remove_user_from_group is rated Critical

Removing a user from a group is an irreversible access control change (the membership is deleted). While the user account itself isn't deleted, group membership removal can immediately revoke access to shared resources, files, and capabilities. This is not merely a 'write' update but a destructive removal of a relationship.

From the tool's definition 'Remove a Nextcloud user from a group' — removes an existing membership relationship; requires admin privileges, indicating significant system impact

Risk signalsAdmin/system-level operation

Questions about remove_user_from_group

What does the remove_user_from_group tool do? +

Remove a Nextcloud user from a group. Requires admin privileges. 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 remove_user_from_group? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for remove_user_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 AIquila — Nextcloud MCP Server. Nothing to install.

What risk level is remove_user_from_group? +

remove_user_from_group 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 remove_user_from_group? +

Yes. Add a rate_limit block to the remove_user_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.

How do I block remove_user_from_group completely? +

Set action: deny in the PolicyLayer policy for remove_user_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.

What MCP server provides remove_user_from_group? +

remove_user_from_group 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.