New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_relation

Delete relation(s) between project entities

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server
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/1999azzar-project-guardian-mcp-server/delete-relation.md

What delete_relation does on Project Guardian MCP

AI agents call delete_relation to permanently remove resources in Project Guardian MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_relation is rated Critical

This tool permanently removes relationship data from the project memory system. Deletion operations are irreversible and cannot be undone through normal API operations. While the blast radius is scoped to relation data rather than entities themselves, the destruction of knowledge graph connections could break workflow dependencies and lose important project context.

From the tool's definition Tool name is 'delete_relation' with description 'Delete relation(s) between project entities'. The verb 'delete' combined with the function of removing relations from a knowledge graph represents irreversible data deletion.

Questions about delete_relation

What does the delete_relation tool do? +

Delete relation(s) between project entities. It is categorised as a Destructive tool in the Project Guardian MCP 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_relation? +

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

What risk level is delete_relation? +

delete_relation 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_relation? +

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

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

delete_relation is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Project Guardian, 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 Project Guardian'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.