New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

run_setup_checks

Run Nextcloud setup checks to verify system configuration (security, performance, PHP modules, etc.). Requires admin privileges

High RISK CLASS
Category Execute
Parameters 00 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-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

Questions about run_setup_checks

What does the run_setup_checks tool do? +

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.

How do I enforce a policy on run_setup_checks? +

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.

What risk level is run_setup_checks? +

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

Can I rate-limit run_setup_checks? +

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.

How do I block run_setup_checks completely? +

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.

What MCP server provides run_setup_checks? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AIquila — Nextcloud MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.