audit_events_prune
Run audit-events.prune through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/audit-events-prune.md
What audit_events_prune does on Appaloft
AI agents call audit_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 | — | |
eventType | string | — | |
aggregateId | string | — |
Parameters from the server's own tool schema.
Why audit_events_prune is rated Critical
'Prune' operations are generally irreversible deletions of data (audit event records in this case). Audit logs are critical for compliance and security investigations; permanently removing them constitutes a destructive action with high blast radius if misused. The sibling tool 'audit_events_archives_prune' further confirms that pruning is a distinct destructive operation in this server's catalog.
From the tool's definition 'prune' in the tool name, described as running 'audit-events.prune' — pruning typically means irreversibly removing/deleting old or excess records
Attacks that exploit this kind of access
The rule that runs audit_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 audit_events_prune, this is the rule to start with:
audit_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 audit_events_prune call is checked against it from then on.
Questions about audit_events_prune
Run audit-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.
audit_events_prune accepts 4 parameters: before, dryRun, eventType, aggregateId. 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 audit_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.
audit_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 audit_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 audit_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.
audit_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