kg_delete_entity

Delete an entity and all its relationships and observations from the knowledge graph.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/kg-delete-entity.md

What kg_delete_entity does on CoWork OS

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

Why kg_delete_entity is rated Critical

This tool permanently removes data (entities, relationships, observations) from a knowledge graph. The deletion is irreversible and destroys linked information. While not system-critical like a financial transfer or OS-level command, it causes permanent data loss within the application's knowledge system.

From the tool's definition Tool name 'kg_delete_entity' and description states it will 'Delete an entity and all its relationships and observations from the knowledge graph' — this is an irreversible deletion operation that removes data and cannot be undone.

Questions about kg_delete_entity

What does the kg_delete_entity tool do? +

Delete an entity and all its relationships and observations from the knowledge graph. It is categorised as a Destructive tool in the CoWork OS 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 kg_delete_entity? +

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

What risk level is kg_delete_entity? +

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

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

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

kg_delete_entity is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on CoWork OS, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CoWork OS's. Pull the full record:

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.