Reads current UnClick Orchestrator continuity so a seat can interpret a freshly saved turn before acting. Use immediately after save_conversation_turn in the required Log -> Read -> Decide -> Reply -> Log reply gate. If this read fails, say CONTEXT_UNREAD or UNTETHERED instead of guessing whether...
AI agents call read_orchestrator_context to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Optional search text from the saved turn. Do not include secrets. |
limit | number | — | Maximum events to read. |
compact | boolean | — | Return compact source summaries by default. |
include_raw | boolean | — | Include raw fields when explicitly needed. |
max_summaries | number | — | Maximum compact summaries to return when compact mode is on. |
Parameters from the server's own tool schema.
This tool retrieves and reads state information from the UnClick Orchestrator system. It performs a query-like operation to fetch the current context/continuity state, enabling interpretation of prior conversation turns. This is fundamentally a Read operation — it gathers data to inform decision-making but does not modify, execute external commands, delete data, or incur financial obligations.
From the tool's definition Tool name is 'read_orchestrator_context' and description explicitly states 'Reads current UnClick Orchestrator continuity' — a retrieval operation with 'no side effects.' The description emphasizes reading/interpreting saved state without modification.
Attacks that exploit this kind of access
Reads current UnClick Orchestrator continuity so a seat can interpret a freshly saved turn before acting. Use immediately after save_conversation_turn in the required Log -> Read -> Decide -> Reply -> Log reply gate. If this read fails, say CONTEXT_UNREAD or UNTETHERED instead of guessing whether a phrase is a test cue, real request, blocker, proof, or status. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
read_orchestrator_context accepts 5 parameters: q, limit, compact, include_raw, max_summaries. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for read_orchestrator_context: 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 UnClick. Nothing to install.
read_orchestrator_context 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 read_orchestrator_context 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 read_orchestrator_context. 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.
read_orchestrator_context is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →