add_user_to_group
Add a Nextcloud user to a group. Requires admin privileges
This record as markdown: /tools/aiquila-nextcloud-mcp-server/add-user-to-group.md
What add_user_to_group does on AIquila — Nextcloud MCP Server
AI agents use add_user_to_group to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
userId | string | Yes | The user ID (login name) to add to the group |
groupId | string | Yes | The group ID (name) to add the user to |
Parameters from the server's own tool schema.
Why add_user_to_group is rated Medium
This tool modifies user group assignments, which is a reversible Write operation. Although it requires elevated privileges, it does not delete data, execute arbitrary code, or move money. The 'high' severity reflects that unauthorized group membership changes could grant an attacker access to shared resources and permissions throughout the Nextcloud instance.
From the tool's definition Tool name 'add_user_to_group' and description 'Add a Nextcloud user to a group' indicates creation/modification of group membership relationships. Requires admin privileges.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs add_user_to_group 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 add_user_to_group, this is the rule to start with:
add_user_to_group stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every add_user_to_group call is checked against it from then on.
Questions about add_user_to_group
Add a Nextcloud user to a group. Requires admin privileges. It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_user_to_group accepts 2 parameters: userId, groupId. Required: userId, groupId. 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 add_user_to_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.
add_user_to_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_user_to_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 add_user_to_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.
add_user_to_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.
This server
Across the catalogue