get_out_of_office
Get a user's current out-of-office / absence status (NC 28+)
This record as markdown: /tools/aiquila-nextcloud-mcp-server/get-out-of-office.md
What get_out_of_office does on AIquila — Nextcloud MCP Server
AI agents call get_out_of_office 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 | — | User ID to check (defaults to the configured Nextcloud user) |
Parameters from the server's own tool schema.
Why get_out_of_office is rated Low
This tool only queries and retrieves absence status information about a user. It performs no write, delete, execute, or financial operations. The read operation has minimal blast radius since it accesses non-sensitive scheduling metadata that is typically already visible to other users in collaborative systems.
From the tool's definition Tool name is 'get_out_of_office' and description states 'Get a user's current out-of-office / absence status' — pure data retrieval with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_out_of_office, this is the rule to start with:
get_out_of_office 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_out_of_office call is checked against it from then on.
Questions about get_out_of_office
Get a user's current out-of-office / absence status (NC 28+). It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
get_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 get_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.
get_out_of_office 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_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 get_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.
get_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.
This server
Across the catalogue