install_app
Install a Nextcloud app from the App Store via occ app:install
This record as markdown: /tools/aiquila-nextcloud-mcp-server/install-app.md
What install_app does on AIquila — Nextcloud MCP Server
AI agents invoke install_app to trigger actions in AIquila — Nextcloud MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
appId | string | Yes | App ID to install (e.g. "tasks", "calendar", "mail") |
keepDisabled | boolean | — | Install but keep the app disabled |
Parameters from the server's own tool schema.
Why install_app is rated High
This tool executes a system-level command (occ app:install) that installs software on the Nextcloud server. This is an Execute category action with high severity because it runs external commands that modify the server environment, could introduce malicious or vulnerable software, and has wide blast radius if misused by an AI agent.
From the tool's definition Install a Nextcloud app from the App Store via occ app:install
Attacks that exploit this kind of access
The rule that runs install_app 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 install_app, this is the rule to start with:
install_app stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 install_app call is checked against it from then on.
Questions about install_app
Install a Nextcloud app from the App Store via occ app:install. It is categorised as a Execute tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
install_app accepts 2 parameters: appId, keepDisabled. Required: appId. 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 install_app: 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.
install_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the install_app 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 install_app. 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.
install_app 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