run_occ

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

High RISK CLASS

Category Execute

Parameters 31 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/run-occ.md

WHAT IT DOES

What run_occ does on AIquila — Nextcloud MCP Server

AI agents invoke run_occ 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
`args`	array	—	Optional arguments for the command (e.g., ["--shipped=false", "--output=json"])
`command`	string	Yes	The OCC command to execute (e.g., "app:list", "config:list", "setupchecks")
`timeout`	number	—	Timeout in seconds (default: 120, max: 600)

Parameters from the server's own tool schema.

RISK

Why run_occ is rated High

While the allowlist constrains which commands may run (mitigating risk), the tool fundamentally executes arbitrary OCC commands against the Nextcloud server. Commands like 'files:scan', 'trashbin:cleanup', 'db:add-missing-indices', and 'maintenance:mode' trigger administrative operations that alter server state and behavior. A malicious prompt could craft inputs to these allowed commands with harmful side effects (e.

From the tool's definition Tool name 'run_occ' and description state it 'Execute[s] an allowlisted Nextcloud OCC command on the server and return the output.' The verb 'Execute' and the fact that it runs server commands—even with an allowlist—means it triggers external operations whose…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_occ 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 run_occ, this is the rule to start with:

run_occ Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_occ": {
      "limits": [
        {
          "counter": "run_occ_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every run_occ call is checked against it from then on.

FAQ

Questions about run_occ

What does the run_occ tool do? +

Execute an allowlisted Nextcloud OCC command on the server and return the output. Only commands in the allowlist may be run (configurable via MCP_OCC_ALLOWLIST env var). Allowed by default: status, app:list, app:check-code, config:app:get, setupchecks, integrity:check-core, integrity:check-app, user:list, user:info, group:list, maintenance:mode, maintenance:mimetype:update-db, db:add-missing-indices, db:add-missing-columns, db:add-missing-primary-keys, files:scan, files:cleanup, trashbin:cleanup, update:check, notification:generate, theming:config. 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.

What parameters does run_occ accept? +

run_occ accepts 3 parameters: args, command, timeout. Required: command. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_occ? +

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

run_occ is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_occ? +

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

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

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

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 301 AIquila — Nextcloud MCP Server tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →