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

run_coworker

Run a coworker immediately (synchronously) and return the run result.

High RISK CLASS
Category Execute
Parameters 11 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-coworker.md

What run_coworker does on AIquila — Nextcloud MCP Server

AI agents invoke run_coworker 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.

ParameterTypeRequiredDescription
id number Yes Coworker ID

Parameters from the server's own tool schema.

Why run_coworker is rated High

This tool executes external operations whose side effects are contingent on the coworker's implementation and arguments. While the exact nature of 'coworker' is somewhat opaque (could be a task, workflow, or script), the verb 'run' paired with synchronous execution and result return clearly indicates it triggers code/process execution rather than simple data retrieval or modification.

From the tool's definition Tool name 'run_coworker' combined with description 'Run a coworker immediately (synchronously) and return the run result' indicates execution of an external operation.

Questions about run_coworker

What does the run_coworker tool do? +

Run a coworker immediately (synchronously) and return the run result. 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_coworker accept? +

run_coworker accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_coworker? +

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

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

Can I rate-limit run_coworker? +

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

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

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