Run retention cleanup for closed privacy program artifacts.
AI agents call run_privacy_retention to permanently remove resources in ComplyOS — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Retention cleanup operations are typically irreversible deletions of stored records/artifacts. Removing privacy program artifacts permanently falls under Destructive. High severity because misuse could permanently destroy compliance audit trails and privacy records that may be legally required.
From the tool's definition 'Run retention cleanup for closed privacy program artifacts' — 'cleanup' of 'closed privacy program artifacts' implies irreversible deletion or purging of data
Attacks that exploit this kind of access
Run retention cleanup for closed privacy program artifacts. It is categorised as a Destructive tool in the ComplyOS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ComplyOS MCP server in PolicyLayer and add a rule for run_privacy_retention: 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 ComplyOS. Nothing to install.
run_privacy_retention 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 run_privacy_retention 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 run_privacy_retention. 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.
run_privacy_retention is provided by the ComplyOS MCP server (simongonzalezdc/complyos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →