Get orchestrator status — worker slots, task queue, active/completed tasks.
AI agents call orchestrator_status to retrieve information from ScreenHand without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves status information about the orchestrator's internal state (worker slots, queues, task history). This is a pure information retrieval operation with no side effects, no code execution, and no data modification. It falls squarely into the Read category. The low severity reflects that exposing status information has minimal blast radius—an AI agent cannot cause harm by querying this data.
From the tool's definition Tool description states 'Get orchestrator status' with operations limited to retrieving 'worker slots, task queue, active/completed tasks' — all read/query operations with no data modification.
Documented attack patterns abuse exactly the kind of access orchestrator_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScreenHand, and nothing reaches the server without passing your rules. This is the rule we recommend for orchestrator_status:
{
"version": "1",
"default": "deny",
"tools": {
"orchestrator_status": {}
}
}orchestrator_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get orchestrator status — worker slots, task queue, active/completed tasks. It is categorised as a Read tool in the ScreenHand MCP Server, which means it retrieves data without modifying state.
Register the ScreenHand MCP server in PolicyLayer and add a rule for orchestrator_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 ScreenHand. Nothing to install.
orchestrator_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the orchestrator_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.
Set action: deny in the PolicyLayer policy for orchestrator_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.
orchestrator_status is provided by the ScreenHand MCP server (manushi4/screenhand). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScreenHand, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 ScreenHand tools catalogued and risk-classified — across an index of 43,000+ MCP servers.