clear_out_of_office
Clear a user's out-of-office / absence status (NC 28+)
This record as markdown: /tools/aiquila-nextcloud-mcp-server/clear-out-of-office.md
What clear_out_of_office does on AIquila — Nextcloud MCP Server
AI agents call clear_out_of_office 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
userId | string | — | User ID to clear absence for (defaults to the configured Nextcloud user) |
Parameters from the server's own tool schema.
Why clear_out_of_office is rated Critical
Clearing an out-of-office status irreversibly removes the current absence configuration without a built-in undo mechanism. While the user can re-enter the information, the act of clearing destroys the existing data. Severity is medium because the blast radius is limited to a single user's calendar/absence status, but misuse could cause missed communications or inappropriate availability signals.
From the tool's definition Clear a user's out-of-office / absence status
Attacks that exploit this kind of access
The rule that runs clear_out_of_office 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 clear_out_of_office, this is the rule to start with:
clear_out_of_office is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every clear_out_of_office call is checked against it from then on.
Questions about clear_out_of_office
Clear a user's out-of-office / absence status (NC 28+). 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.
clear_out_of_office accepts 1 parameter: 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 clear_out_of_office: 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.
clear_out_of_office is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_out_of_office 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 clear_out_of_office. 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.
clear_out_of_office 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