domain_events_prune
Run domain-events.prune through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/domain-events-prune.md
What domain_events_prune does on Appaloft
AI agents call domain_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 |
|---|---|---|---|
limit | integer | — | |
before | string | Yes | |
dryRun | boolean | — | |
eventType | string | — | |
aggregateId | string | — | |
deploymentId | string | — | |
aggregateType | string | — |
Parameters from the server's own tool schema.
Why domain_events_prune is rated Critical
The term 'prune' consistently indicates irreversible deletion of data (removing old or excess records). Combined with the pattern seen in sibling tools like 'audit_events_archives_prune', this tool almost certainly deletes domain event data permanently. This is a Destructive action with high severity since bulk event log deletion cannot be undone and may affect audit trails or compliance records.
From the tool's definition 'prune' in 'domain_events_prune' and 'Run domain-events.prune' — pruning implies irreversible removal of domain event records
Attacks that exploit this kind of access
The rule that runs domain_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 domain_events_prune, this is the rule to start with:
domain_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 domain_events_prune call is checked against it from then on.
Questions about domain_events_prune
Run domain-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.
domain_events_prune accepts 7 parameters: limit, before, dryRun, eventType, aggregateId, deploymentId, aggregateType. 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 domain_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.
domain_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 domain_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 domain_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.
domain_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