Critical-risk tools in Knowledge Graph Server
4 of the 15 tools in Knowledge Graph Server are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete_edgeDestructive 4/5Delete edges from the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools, and the operation cannot be undone. Use cases: 1. Delet...
-
delete_nodeDestructive 4/5Delete nodes from the knowledge graph. This tool must be used in conjunction with list_graphs tool, and the operation cannot be undone. Use cases: 1. Delete incorrectly created ...
-
delete_resourceDestructive 4/5Delete resources from the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools, and the operation cannot be undone. Use cases: 1. D...
-
unlink_resourceDestructive 4/5Unlink resource associations from nodes. This tool must be used in conjunction with list_graphs and get_node_details tools. Use cases: 1. Adjust resource associations 2. Remove ...
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Knowledge Graph Server
Enforce policy on Knowledge Graph Server
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init