disable_user
Disable a Nextcloud user account (prevents login but preserves data). Requires admin privileges
This record as markdown: /tools/aiquila-nextcloud-mcp-server/disable-user.md
What disable_user does on AIquila — Nextcloud MCP Server
AI agents use disable_user 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 disable |
Parameters from the server's own tool schema.
Why disable_user is rated Medium
This tool modifies account status reversibly rather than irreversibly destroying data, so it falls under Write rather than Destructive. However, it carries high severity because disabling a user account is a significant administrative action that could block legitimate access, affect business continuity, and requires admin privileges.
From the tool's definition Tool description states 'Disable a Nextcloud user account (prevents login but preserves data)' — this modifies user account state reversibly (disabling is not permanent deletion, and data is preserved).
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs disable_user 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 disable_user, this is the rule to start with:
disable_user 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 disable_user call is checked against it from then on.
Questions about disable_user
Disable a Nextcloud user account (prevents login but preserves data). 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.
disable_user accepts 1 parameter: userId. Required: userId. 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 disable_user: 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.
disable_user 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 disable_user 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 disable_user. 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.
disable_user 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