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

get_coworker_runs

Get recent run history (progress, status, summary) for a coworker.

Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/get-coworker-runs.md

What get_coworker_runs does on AIquila — Nextcloud MCP Server

AI agents call get_coworker_runs to retrieve information from AIquila — Nextcloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
id number Yes Coworker ID
limit number — Max runs to return (default 20)

Parameters from the server's own tool schema.

Why get_coworker_runs is rated Low

This tool queries and retrieves historical data about a coworker's runs without creating, modifying, deleting, or executing any operations. It is purely informational, making it a Read category tool with low severity since viewing historical run data poses minimal risk even if misused.

From the tool's definition Tool retrieves 'recent run history (progress, status, summary)' for a coworker—a read-only query operation with no side effects or data modification.

Questions about get_coworker_runs

What does the get_coworker_runs tool do? +

Get recent run history (progress, status, summary) for a coworker. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_coworker_runs accept? +

get_coworker_runs accepts 2 parameters: id, limit. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_coworker_runs? +

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

get_coworker_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_coworker_runs? +

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

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

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