deployments_cleanup_preview
Run deployments.cleanup-preview through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/deployments-cleanup-preview.md
What deployments_cleanup_preview does on Appaloft
AI agents call deployments_cleanup_preview 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 |
|---|---|---|---|
trustedContext | object | — | |
sourceFingerprint | string | Yes |
Parameters from the server's own tool schema.
Why deployments_cleanup_preview is rated Low
The word 'preview' strongly implies this is a read/dry-run operation that shows what would be cleaned up without actually performing the deletion. Preview operations typically enumerate or display candidates for action without side effects. However, confidence is moderate because the description is minimal and 'cleanup' could imply some preparatory write action depending on implementation.
From the tool's definition 'cleanup-preview' suggests a preview/dry-run of a cleanup operation, not the actual destructive action itself
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs deployments_cleanup_preview 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_cleanup_preview, this is the rule to start with:
deployments_cleanup_preview 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_cleanup_preview call is checked against it from then on.
Questions about deployments_cleanup_preview
Run deployments.cleanup-preview 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_cleanup_preview accepts 2 parameters: trustedContext, sourceFingerprint. Required: sourceFingerprint. 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_cleanup_preview: 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_cleanup_preview 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_cleanup_preview 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_cleanup_preview. 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_cleanup_preview 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