deployments_timeline_stream
Read deployments.timeline.stream through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/deployments-timeline-stream.md
What deployments_timeline_stream does on Appaloft
AI agents call deployments_timeline_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 |
|---|---|---|---|
kinds | array | — | |
limit | integer | — | |
cursor | string | — | |
follow | object | — | |
sources | array | — | |
deploymentId | string | Yes | |
untilTerminal | object | — | |
includeHistory | object | — |
Parameters from the server's own tool schema.
Why deployments_timeline_stream is rated Low
This tool queries deployment timeline data and streams it to the caller. It retrieves information with no side effects, no data modification, no code execution, and no destructive or financial impact. It is a straightforward Read operation with low risk if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Read deployments.timeline.stream' — a retrieval operation. The verb 'Read' in the description and the operation name 'stream' (which retrieves a timeline of deployment events) confirm a read-only, non-modifying action.
Attacks that exploit this kind of access
The rule that runs deployments_timeline_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 deployments_timeline_stream, this is the rule to start with:
deployments_timeline_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 deployments_timeline_stream call is checked against it from then on.
Questions about deployments_timeline_stream
Read deployments.timeline.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.
deployments_timeline_stream accepts 8 parameters: kinds, limit, cursor, follow, sources, deploymentId, untilTerminal, includeHistory. Required: deploymentId. 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 deployments_timeline_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.
deployments_timeline_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 deployments_timeline_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 deployments_timeline_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.
deployments_timeline_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