ragflow_update_chunk_tool · RAGFlow MCP Server MCP

WHAT IT DOES

What ragflow_update_chunk_tool does on RAGFlow MCP Server

AI agents use ragflow_update_chunk_tool to create or update resources in RAGFlow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RAGFlow MCP Server environment.

WHY IT NEEDS A POLICY

Why ragflow_update_chunk_tool needs a policy

The 'update' prefix and 'chunk' target indicate this tool modifies existing data reversibly (Write category). This is not Destructive because updates are typically reversible through additional updates. It carries medium severity because misuse could corrupt or pollute a knowledge base with incorrect information, affecting downstream RAG operations and AI model responses.

From the tool's definition Tool name contains 'update_chunk' which indicates modification of data chunks within a RAGFlow dataset. Sibling tools include 'ragflow_add_chunk_tool', 'ragflow_delete_chunk_tool', and 'ragflow_delete_dataset_tool', contextualizing this as a data manipulation…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ragflow_update_chunk_tool Rate-limited

ragflow_update_chunk_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ragflow_update_chunk_tool": {
      "limits": [
        {
          "counter": "ragflow_update_chunk_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RAGFlow MCP Server, so you can run agents against it safely.

FAQ

Questions about ragflow_update_chunk_tool

What does the ragflow_update_chunk_tool tool do? +

ragflow_update_chunk_tool. It is categorised as a Write tool in the RAGFlow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ragflow_update_chunk_tool? +

Register the RAGFlow MCP Server MCP server in PolicyLayer and add a rule for ragflow_update_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.

What risk level is ragflow_update_chunk_tool? +

ragflow_update_chunk_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ragflow_update_chunk_tool? +

Yes. Add a rate_limit block to the ragflow_update_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.

How do I block ragflow_update_chunk_tool completely? +

Set action: deny in the PolicyLayer policy for ragflow_update_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.

What MCP server provides ragflow_update_chunk_tool? +

ragflow_update_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.