ragflow_delete_chunk_tool
AI agents call ragflow_delete_chunk_tool to permanently remove resources in RAGFlow MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' prefix unambiguously indicates a destructive action that cannot be undone. Deleting document chunks from a RAGFlow knowledge base irreversibly removes portions of the managed dataset. Although the description is empty, the name is sufficiently explicit.
From the tool's definition Tool name: 'ragflow_delete_chunk_tool' — the verb 'delete' indicates irreversible removal of data. The tool operates on 'chunks' (document fragments in RAGFlow's knowledge base), which are stored data artifacts.
Attacks that exploit this kind of access
ragflow_delete_chunk_tool. It is categorised as a Destructive tool in the RAGFlow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RAGFlow MCP Server MCP server in PolicyLayer and add a rule for ragflow_delete_chunk_tool: 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 RAGFlow MCP Server. Nothing to install.
ragflow_delete_chunk_tool 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 ragflow_delete_chunk_tool 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 ragflow_delete_chunk_tool. 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.
ragflow_delete_chunk_tool is provided by the RAGFlow MCP Server MCP server (migoxv/ragflow-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 →