knowledge_clear
DESTRUCTIVE: Clear all knowledge from the vector store. This removes all ingested documents but does not delete the original files. Set confirm=True to proceed.
This record as markdown: /tools/0xcjt-templonixlite/knowledge-clear.md
What knowledge_clear does on Templonix Lite MCP Server
AI agents call knowledge_clear to permanently remove resources in Templonix Lite MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why knowledge_clear is rated Critical
This tool irreversibly deletes all ingested knowledge documents from the vector store. While original files are preserved, the indexed knowledge is permanently removed and cannot be recovered without re-ingesting. This is a destructive operation with significant blast radius if invoked unintentionally by an AI agent, as it would eliminate all stored knowledge context.
From the tool's definition Tool name is 'knowledge_clear' and description explicitly states 'DESTRUCTIVE: Clear all knowledge from the vector store. This removes all ingested documents' with a confirmation flag required.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs knowledge_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Templonix Lite MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For knowledge_clear, this is the rule to start with:
knowledge_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Templonix Lite MCP Server, apply this rule, and every knowledge_clear call is checked against it from then on.
Questions about knowledge_clear
DESTRUCTIVE: Clear all knowledge from the vector store. This removes all ingested documents but does not delete the original files. Set confirm=True to proceed. It is categorised as a Destructive tool in the Templonix Lite MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Templonix Lite MCP Server MCP server in PolicyLayer and add a rule for knowledge_clear: 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 Templonix Lite MCP Server. Nothing to install.
knowledge_clear 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 knowledge_clear 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 knowledge_clear. 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.
knowledge_clear is provided by the Templonix Lite MCP Server MCP server (0xcjt/templonixlite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Templonix Lite MCP Server, and thousands of servers like it.
Across the catalogue