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

set_user_status

Set the current user's status type (online, away, dnd, invisible, offline)

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/set-user-status.md

What set_user_status does on AIquila — Nextcloud MCP Server

AI agents use set_user_status 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
statusType string Yes Status type to set

Parameters from the server's own tool schema.

Why set_user_status is rated Medium

The tool changes the user's status state, which is a data modification operation. This is reversible (status can be changed again), and the blast radius is minimal — only the current user's presence indicator is affected, with no side effects on other systems, data deletion, code execution, or financial implications. Low severity reflects the benign nature of presence status changes.

From the tool's definition Tool description states 'Set the current user's status type' — this modifies user status data (online, away, dnd, invisible, offline). The verb 'set' and the presence of status options confirm a write operation that creates or modifies data reversibly.

Questions about set_user_status

What does the set_user_status tool do? +

Set the current user's status type (online, away, dnd, invisible, offline). 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 set_user_status accept? +

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

How do I enforce a policy on set_user_status? +

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

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

Can I rate-limit set_user_status? +

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

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

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