Get chunks with references from a specific document
AI agents call ragflow_get_chunks to retrieve information from RAGFlow Claude MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves document chunks (likely segments of text with citation metadata) from a knowledge base. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. It is a straightforward data retrieval operation consistent with the Read category, with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'ragflow_get_chunks' and description 'Get chunks with references from a specific document' indicate data retrieval operation. The verb 'Get' and absence of any modification, deletion, or execution language confirm this is a read-only query.
Documented attack patterns abuse exactly the kind of access ragflow_get_chunks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAGFlow Claude MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ragflow_get_chunks:
{
"version": "1",
"default": "deny",
"tools": {
"ragflow_get_chunks": {}
}
} ragflow_get_chunks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get chunks with references from a specific document. It is categorised as a Read tool in the RAGFlow Claude MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RAGFlow Claude MCP Server MCP server in PolicyLayer and add a rule for ragflow_get_chunks: 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 Claude MCP Server. Nothing to install.
ragflow_get_chunks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ragflow_get_chunks 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_get_chunks. 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_get_chunks is provided by the RAGFlow Claude MCP Server MCP server (norandom/ragflow-claude-desktop-local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RAGFlow Claude MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 RAGFlow Claude MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.