get_user_info
Get detailed information about a specific Nextcloud user. Non-admin users can only query their own user ID
This record as markdown: /tools/aiquila-nextcloud-mcp-server/get-user-info.md
What get_user_info does on AIquila — Nextcloud MCP Server
AI agents call get_user_info to retrieve information from AIquila — Nextcloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
userId | string | Yes | The user ID (login name) to get information about |
Parameters from the server's own tool schema.
Why get_user_info is rated Low
This tool retrieves user profile information without creating, modifying, deleting, or executing any operations. The access restriction to self-queries for non-admin users also limits potential data exposure to low severity. Classification as Read is appropriate.
From the tool's definition Tool name: 'get_user_info'; description: 'Get detailed information about a specific Nextcloud user.' The verb 'Get' and explicit statement that the tool retrieves information without modification confirms a read-only operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_user_info 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 get_user_info, this is the rule to start with:
get_user_info is read-only, so it stays allowed. 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 get_user_info call is checked against it from then on.
Questions about get_user_info
Get detailed information about a specific Nextcloud user. Non-admin users can only query their own user ID. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
get_user_info 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 get_user_info: 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.
get_user_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_user_info 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 get_user_info. 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.
get_user_info 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