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

enable_user

Enable a disabled Nextcloud user account. 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/enable-user.md

What enable_user does on AIquila — Nextcloud MCP Server

AI agents use enable_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 enable

Parameters from the server's own tool schema.

Why enable_user is rated Medium

Enabling a user account modifies system state (user access permissions) reversibly—the action can be undone by disabling the account again. This fits the Write category (creates or modifies data reversibly). Severity is high because it grants account access and requires admin privileges, creating potential for unauthorized access if misused by an AI agent, but it is not destructive, financial, or code execution.

From the tool's definition Tool name is 'enable_user' and description states it 'Enable a disabled Nextcloud user account' with 'Requires admin privileges'. This modifies user account state by re-enabling access.

Risk signalsAdmin/system-level operation

Questions about enable_user

What does the enable_user tool do? +

Enable a disabled Nextcloud user account. 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 enable_user accept? +

enable_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 enable_user? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for enable_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 enable_user? +

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

Can I rate-limit enable_user? +

Yes. Add a rate_limit block to the enable_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 enable_user completely? +

Set action: deny in the PolicyLayer policy for enable_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 enable_user? +

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