List sessions for a RAGFlow chat assistant.
AI agents call ragflow_list_sessions_tool to retrieve information from RAGFlow 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 and enumerates existing chat sessions associated with a RAGFlow assistant. It performs a query-only operation without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal — an attacker could enumerate sessions to discover conversation history or metadata, but cannot alter or delete data. This is a standard Read category operation.
From the tool's definition Tool name contains 'list' and description states 'List sessions' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List sessions for a RAGFlow chat assistant. It is categorised as a Read tool in the RAGFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RAGFlow MCP Server MCP server in PolicyLayer and add a rule for ragflow_list_sessions_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_list_sessions_tool 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_list_sessions_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_list_sessions_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_list_sessions_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 →