sandboxes_agents_runs_events
Read sandboxes.agents.runs.events through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandboxes-agents-runs-events.md
What sandboxes_agents_runs_events does on Appaloft
AI agents call sandboxes_agents_runs_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 |
|---|---|---|---|
limit | integer | — | |
runId | string | Yes | |
afterSequence | integer | — |
Parameters from the server's own tool schema.
Why sandboxes_agents_runs_events is rated Low
This tool retrieves or queries event data from sandbox agent runs with no side effects or ability to modify state. The explicit use of 'Read' in the description confirms it performs a data retrieval operation only.
From the tool's definition Tool name and description both indicate a read operation: 'Read sandboxes.agents.runs.events' and the verb 'Read' appears explicitly in the description. No creation, modification, deletion, or execution keywords are present.
Attacks that exploit this kind of access
The rule that runs sandboxes_agents_runs_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 sandboxes_agents_runs_events, this is the rule to start with:
sandboxes_agents_runs_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 sandboxes_agents_runs_events call is checked against it from then on.
Questions about sandboxes_agents_runs_events
Read sandboxes.agents.runs.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.
sandboxes_agents_runs_events accepts 3 parameters: limit, runId, afterSequence. Required: runId. 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_agents_runs_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.
sandboxes_agents_runs_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 sandboxes_agents_runs_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 sandboxes_agents_runs_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.
sandboxes_agents_runs_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