get_user_info

Get detailed information about a specific Nextcloud user. Non-admin users can only query their own user ID

Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Why get_user_info is rated Low

This tool retrieves user information without creating, modifying, or deleting data. It has no side effects and is explicitly read-only. The access restriction (non-admin users limited to their own data) further mitigates risk. Severity is low because the blast radius is confined to querying existing user metadata, which is non-sensitive in most contexts and properly access-controlled.

From the tool's definition Tool name 'get_user_info' and description 'Get detailed information about a specific Nextcloud user' indicate data retrieval with no modification.

Risk signalsAdmin/system-level operation

Questions about get_user_info

What does the get_user_info tool do? +

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.

How do I enforce a policy on get_user_info? +

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.

What risk level is get_user_info? +

get_user_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_user_info? +

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.

How do I block get_user_info completely? +

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.

What MCP server provides get_user_info? +

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.

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