operator_work_stream_events
Read operator-work.stream-events through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/operator-work-stream-events.md
What operator_work_stream_events does on Appaloft
AI agents call operator_work_stream_events to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cursor | string | — | |
follow | object | — | |
workId | string | Yes | |
historyLimit | integer | — | |
untilTerminal | object | — | |
includeHistory | object | — | |
pollIntervalMs | integer | — |
Parameters from the server's own tool schema.
Why operator_work_stream_events is rated Low
Even though operator_work_stream_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs operator_work_stream_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For operator_work_stream_events, this is the rule to start with:
operator_work_stream_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every operator_work_stream_events call is checked against it from then on.
Questions about operator_work_stream_events
Read operator-work.stream-events through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
operator_work_stream_events accepts 7 parameters: cursor, follow, workId, historyLimit, untilTerminal, includeHistory, pollIntervalMs. Required: workId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for operator_work_stream_events: 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 Appaloft. Nothing to install.
operator_work_stream_events 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 operator_work_stream_events 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 operator_work_stream_events. 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.
operator_work_stream_events is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue