AI agents call clear_index to permanently remove resources in MCP-Markdown-RAG — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This operation irreversibly deletes all indexed vector data, preventing future semantic search across the document collection. While the original markdown files may still exist, the index itself—a computed derivative—is permanently destroyed. This fits the Destructive category as it represents an action that cannot be undone without manual re-indexing.
From the tool's definition Tool name 'clear_index' combined with description 'Clear the vector database' indicates irreversible deletion of indexed data.
Documented attack patterns abuse exactly the kind of access clear_index gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Markdown-RAG, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_index:
{
"version": "1",
"default": "deny",
"hide": [
"clear_index"
]
}clear_index 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.
Clear the vector database. It is categorised as a Destructive tool in the MCP-Markdown-RAG MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP-Markdown-RAG MCP server in PolicyLayer and add a rule for clear_index: 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 MCP-Markdown-RAG. Nothing to install.
clear_index 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_index 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_index. 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_index is provided by the MCP-Markdown-RAG MCP server (zackriya-solutions/mcp-markdown-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 MCP-Markdown-RAG tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 MCP-Markdown-RAG tools catalogued and risk-classified — across an index of 42,500+ MCP servers.