Remove a Knowledge Graph link between two entities.
AI agents call unlink_entities to permanently remove resources in Turbo Quant Memory MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Unlinking entities removes a relationship from the knowledge graph. This operation is irreversible in the sense that the link is deleted without an obvious undo mechanism, qualifying it as Destructive. The blast radius is medium since removing links could degrade the knowledge graph's utility for AI agents (broken relationships, lost context), but it doesn't delete the entities themselves.
From the tool's definition Remove a Knowledge Graph link between two entities
Documented attack patterns abuse exactly the kind of access unlink_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Turbo Quant Memory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for unlink_entities:
{
"version": "1",
"default": "deny",
"hide": [
"unlink_entities"
]
}unlink_entities disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a Knowledge Graph link between two entities. It is categorised as a Destructive tool in the Turbo Quant Memory MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Turbo Quant Memory MCP Server MCP server in PolicyLayer and add a rule for unlink_entities: 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 Turbo Quant Memory MCP Server. Nothing to install.
unlink_entities 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 unlink_entities 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 unlink_entities. 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.
unlink_entities is provided by the Turbo Quant Memory MCP Server MCP server (lexus2016/turbo_quant_memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Turbo Quant Memory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Turbo Quant Memory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.