Delete multiple relations from your DevFlow MCP knowledge graph memory
AI agents call delete_relations to permanently remove resources in DevFlow MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes data (relations) from a persistent knowledge store. This is irreversible deletion, matching the Destructive category definition. Severity is high because an erroneous or malicious deletion could corrupt the agent's understanding of project workflows, dependencies, and context — potentially breaking downstream development decisions — but blast radius is scoped to the local knowledge graph…
From the tool's definition Tool name and description explicitly state 'Delete multiple relations' — this performs irreversible removal of data from the knowledge graph stored in SQLite.
Attacks that exploit this kind of access
Delete multiple relations from your DevFlow MCP knowledge graph memory. It is categorised as a Destructive tool in the DevFlow MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DevFlow MCP server in PolicyLayer and add a rule for delete_relations: 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 DevFlow MCP. Nothing to install.
delete_relations 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 delete_relations 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 delete_relations. 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.
delete_relations is provided by the DevFlow MCP server (takin-profit/devflow-mcp). 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 →