loeschen_auf_verlangen

DSGVO-Löschung einer Blob+Stub-Quelle: vernichtet Blob und Schlüssel, der Stub wird Tombstone. Für Klartext-Altfälle gilt nur die dokumentierte Notfallprozedur.

Server Lokyy oliverhees/lokyy-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What loeschen_auf_verlangen does on Lokyy

AI agents call loeschen_auf_verlangen to permanently remove resources in Lokyy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why loeschen_auf_verlangen needs a policy

This tool performs GDPR-mandated deletion by irreversibly destroying blob data and encryption keys, and converting source stubs to tombstones. This is explicitly irreversible ('vernichtet' = destroys), qualifying as Destructive. The critical severity reflects that misuse would permanently destroy stored data and cryptographic keys with no recovery path.

From the tool's definition DSGVO-Löschung: vernichtet Blob und Schlüssel, der Stub wird Tombstone — irreversible deletion of blob, key, and conversion of stub to tombstone record

Questions about loeschen_auf_verlangen

What does the loeschen_auf_verlangen tool do? +

DSGVO-Löschung einer Blob+Stub-Quelle: vernichtet Blob und Schlüssel, der Stub wird Tombstone. Für Klartext-Altfälle gilt nur die dokumentierte Notfallprozedur. It is categorised as a Destructive tool in the Lokyy 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 loeschen_auf_verlangen? +

Register the Lokyy MCP server in PolicyLayer and add a rule for loeschen_auf_verlangen: 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 Lokyy. Nothing to install.

What risk level is loeschen_auf_verlangen? +

loeschen_auf_verlangen 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 loeschen_auf_verlangen? +

Yes. Add a rate_limit block to the loeschen_auf_verlangen 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 loeschen_auf_verlangen completely? +

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

loeschen_auf_verlangen is provided by the Lokyy MCP server (oliverhees/lokyy-mcp). 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.