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

clear_user_status_message

Clear the current user's custom status message

Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/clear-user-status-message.md

What clear_user_status_message does on AIquila — Nextcloud MCP Server

AI agents call clear_user_status_message to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clear_user_status_message is rated Critical

Clearing a status message removes existing data. While it could be considered a Write (setting to empty), the action is irreversible in the sense that the previous message is lost without recovery. However, the blast radius is low-to-medium since it only affects a user's status message, a relatively minor piece of data.

From the tool's definition 'Clear the current user's custom status message' — removes/deletes the existing status message

Questions about clear_user_status_message

What does the clear_user_status_message tool do? +

Clear the current user's custom status message. It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_user_status_message? +

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

clear_user_status_message is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_user_status_message? +

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

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

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