New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

disable_user

Disable a Nextcloud user account (prevents login but preserves data). Requires admin privileges

Medium RISK CLASS
Category Write
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about disable_user

What does the disable_user tool do? +

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.

What parameters does disable_user accept? +

disable_user accepts 1 parameter: userId. Required: userId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on disable_user? +

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.

What risk level is disable_user? +

disable_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disable_user? +

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.

How do I block disable_user completely? +

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.

What MCP server provides disable_user? +

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.

Across the catalogue

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