disable_coworker
Disable a coworker so it stops running on its schedule.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/disable-coworker.md
What disable_coworker does on AIquila — Nextcloud MCP Server
AI agents invoke disable_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Coworker ID |
Parameters from the server's own tool schema.
Why disable_coworker is rated High
Disabling a coworker halts a scheduled process or automation, which is an operational action with meaningful consequences. It does not delete data (so not Destructive), but it changes the execution state of a running service/job. This falls under Execute as it triggers an external operation. The severity is high because disabling a coworker could disrupt automated workflows or business processes.
From the tool's definition 'Disable a coworker so it stops running on its schedule' — triggers an external operational state change (stopping a scheduled process/job)
Attacks that exploit this kind of access
The rule that runs disable_coworker 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 disable_coworker, this is the rule to start with:
disable_coworker 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 disable_coworker call is checked against it from then on.
Questions about disable_coworker
Disable a coworker so it stops running on its schedule. 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.
disable_coworker accepts 1 parameter: id. Required: id. 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 disable_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.
disable_coworker 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 disable_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.
Set action: deny in the PolicyLayer policy for disable_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.
disable_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.
Across the catalogue