sandboxes_events_stream
Read sandboxes.events.stream through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandboxes-events-stream.md
What sandboxes_events_stream does on Appaloft
AI agents call sandboxes_events_stream 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 |
|---|---|---|---|
limit | integer | — | |
cursor | string | — | |
sandboxId | string | Yes | |
untilTerminal | boolean | — |
Parameters from the server's own tool schema.
Why sandboxes_events_stream is rated Low
The tool retrieves or queries event stream data from sandboxes without side effects. The verb 'Read' in the description and the operation pattern of streaming events (monitoring/observing) clearly indicate this is a data retrieval function with no ability to modify, delete, or execute actions. Severity is low because event stream reading typically has minimal blast radius and does not affect system state.
From the tool's definition Tool name 'sandboxes_events_stream' and description explicitly state 'Read sandboxes.events.stream' indicating retrieval of event stream data with no modification capability.
Attacks that exploit this kind of access
The rule that runs sandboxes_events_stream 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 sandboxes_events_stream, this is the rule to start with:
sandboxes_events_stream 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 sandboxes_events_stream call is checked against it from then on.
Questions about sandboxes_events_stream
Read sandboxes.events.stream 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.
sandboxes_events_stream accepts 4 parameters: limit, cursor, sandboxId, untilTerminal. Required: sandboxId. 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 sandboxes_events_stream: 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.
sandboxes_events_stream 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 sandboxes_events_stream 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 sandboxes_events_stream. 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.
sandboxes_events_stream 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