get_orchestration_status

Get the persisted status of a DAG orchestration run created for the current task.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/get-orchestration-status.md

WHAT IT DOES

What get_orchestration_status does on CoWork OS

AI agents call get_orchestration_status to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_orchestration_status is rated Low

This tool retrieves status information about a DAG (directed acyclic graph) orchestration run. It is a read-only operation that fetches persisted state data. There are no side effects, no code execution, no data modification, and no destructive operations. The minimal blast radius from misuse would be information disclosure about orchestration run status, which is a standard Read category risk.

From the tool's definition Tool name 'get_orchestration_status' and description 'Get the persisted status of a DAG orchestration run' indicate a retrieval operation that queries existing status information without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_orchestration_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_orchestration_status, this is the rule to start with:

get_orchestration_status Allowed

get_orchestration_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_orchestration_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every get_orchestration_status call is checked against it from then on.

FAQ

Questions about get_orchestration_status

What does the get_orchestration_status tool do? +

Get the persisted status of a DAG orchestration run created for the current task. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_orchestration_status? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for get_orchestration_status: 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 CoWork OS. Nothing to install.

What risk level is get_orchestration_status? +

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

Can I rate-limit get_orchestration_status? +

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

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

get_orchestration_status is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →