run_setup_checks
Run Nextcloud setup checks to verify system configuration (security, performance, PHP modules, etc.). Requires admin privileges
This record as markdown: /tools/aiquila-nextcloud-mcp-server/run-setup-checks.md
What run_setup_checks does on AIquila — Nextcloud MCP Server
AI agents invoke run_setup_checks 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.
Why run_setup_checks is rated High
This tool triggers execution of automated diagnostic checks against the Nextcloud system. While the checks themselves are informational (not directly destructive), the tool executes code/processes whose behavior depends on system state and admin-level invocation context. This qualifies as Execute rather than Read because it actively runs checks rather than passively querying data.
From the tool's definition Tool description states 'Run Nextcloud setup checks' which involves executing verification routines against system configuration. Requires admin privileges, indicating elevated access context.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs run_setup_checks 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_setup_checks, this is the rule to start with:
run_setup_checks 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 run_setup_checks call is checked against it from then on.
Questions about run_setup_checks
Run Nextcloud setup checks to verify system configuration (security, performance, PHP modules, etc.). Requires admin privileges. 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.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for run_setup_checks: 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.
run_setup_checks 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 run_setup_checks 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 run_setup_checks. 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.
run_setup_checks 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