delete_privacy_subject

Delete subject data unless blocked by an active legal hold.

Server ComplyOS simongonzalezdc/complyos
Category Destructive
Risk class Critical
Parameters 00 required

What delete_privacy_subject does on ComplyOS

AI agents call delete_privacy_subject 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.

Why delete_privacy_subject needs a policy

This tool irreversibly deletes personal data records. Even though deletion can be blocked by legal holds, the primary function is destructive data removal that cannot be undone. In a compliance context, misuse by an AI agent could result in unauthorized deletion of regulated personal information, violating data protection obligations and creating potential legal/regulatory liability.

From the tool's definition Tool name is 'delete_privacy_subject' and description explicitly states it 'Delete[s] subject data unless blocked by an active legal hold.' The verb 'delete' combined with 'subject data' indicates irreversible removal of personal information.

Questions about delete_privacy_subject

What does the delete_privacy_subject tool do? +

Delete subject data unless blocked by an active legal hold. 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.

How do I enforce a policy on delete_privacy_subject? +

Register the ComplyOS MCP server in PolicyLayer and add a rule for delete_privacy_subject: 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.

What risk level is delete_privacy_subject? +

delete_privacy_subject is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_privacy_subject? +

Yes. Add a rate_limit block to the delete_privacy_subject 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.

How do I block delete_privacy_subject completely? +

Set action: deny in the PolicyLayer policy for delete_privacy_subject. 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.

What MCP server provides delete_privacy_subject? +

delete_privacy_subject 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.