source_events_prune
Run source-events.prune through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/source-events-prune.md
What source_events_prune does on Appaloft
AI agents call source_events_prune to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
before | string | Yes | |
dryRun | boolean | — | |
status | string | — | |
projectId | string | — | |
resourceId | string | — | |
sourceKind | string | — |
Parameters from the server's own tool schema.
Why source_events_prune is rated Critical
'Prune' operations typically remove/delete data that cannot be recovered. Combined with the pattern seen in sibling tools (e.g., audit_events_archives_prune), this tool likely irreversibly deletes or purges source event records. This warrants a Destructive classification with high severity given the potential loss of audit/event data.
From the tool's definition 'prune' in the tool name and description — 'Run source-events.prune' — indicates irreversible removal of source events data
Attacks that exploit this kind of access
The rule that runs source_events_prune 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 source_events_prune, this is the rule to start with:
source_events_prune is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every source_events_prune call is checked against it from then on.
Questions about source_events_prune
Run source-events.prune through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
source_events_prune accepts 6 parameters: before, dryRun, status, projectId, resourceId, sourceKind. Required: before. 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 source_events_prune: 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.
source_events_prune is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the source_events_prune 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 source_events_prune. 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.
source_events_prune 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.
Across the catalogue