clear_graph
AI agents call clear_graph to permanently remove resources in KnowledgeSmith MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
'Clear_graph' strongly suggests bulk deletion or purging of graph data without conditions. Combined with sibling tools like delete_entity_edge and delete_episode, and the server's stated goal of efficient document editing, this tool likely performs irreversible data destruction. The empty description reduces confidence slightly, but the name and operational context point to a destructive action.
From the tool's definition Tool name 'clear_graph' with empty description; context indicates this server manages structured RBT documents with complete CRUD functionality including delete operations (delete_entity_edge, delete_episode).
Attacks that exploit this kind of access
clear_graph. It is categorised as a Destructive tool in the KnowledgeSmith MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the KnowledgeSmith MCP server in PolicyLayer and add a rule for clear_graph: 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 KnowledgeSmith MCP. Nothing to install.
clear_graph 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 clear_graph 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 clear_graph. 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.
clear_graph is provided by the KnowledgeSmith MCP server (leo7nel23/knowledgesmith-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 →