ragflow_parse_document_tool
AI agents invoke ragflow_parse_document_tool to trigger actions in RAGFlow MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Document parsing is an Execute category action because it runs a parsing operation/algorithm whose effects depend on the document arguments provided. While not Write (doesn't persistently store) or Destructive (doesn't delete), it performs computation/transformation. Confidence is moderate (0.72) due to empty description—a more detailed specification would clarify if this is read-only retrieval vs.
From the tool's definition Tool name 'ragflow_parse_document_tool' indicates document parsing; sibling tools show this server handles document chunks, datasets, and knowledge base management.
Attacks that exploit this kind of access
ragflow_parse_document_tool. It is categorised as a Execute tool in the RAGFlow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RAGFlow MCP Server MCP server in PolicyLayer and add a rule for ragflow_parse_document_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_parse_document_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ragflow_parse_document_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_parse_document_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_parse_document_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 →