Stop an active parsing job.
AI agents invoke ragflow_stop_parsing_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.
Stopping an active parsing job is an action that interrupts an ongoing operation. While not destructive (the parsed data is not deleted) and not financial, it is an execution-class action because it triggers a state change in an external system.
From the tool's definition Tool name and description indicate it 'Stop[s] an active parsing job' — this is a command that triggers an external operation (halting an in-progress process) whose effect depends on which job is targeted.
Attacks that exploit this kind of access
Stop an active parsing job. 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_stop_parsing_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_stop_parsing_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_stop_parsing_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_stop_parsing_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_stop_parsing_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 →