Stream query results from LightRAG in real-time
AI agents call query_text_stream to retrieve information from LightRAG 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 returns query results from a knowledge graph without creating, modifying, or deleting data. Streaming results is a read operation with no side effects. Low severity because misuse would only expose existing data rather than modify systems or cause irreversible damage.
From the tool's definition Tool name contains 'query' and description states 'Stream query results' with no mention of modification, deletion, or execution of external operations. The verb 'stream' indicates data retrieval.
Attacks that exploit this kind of access
Stream query results from LightRAG in real-time. It is categorised as a Read tool in the LightRAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LightRAG MCP Server MCP server in PolicyLayer and add a rule for query_text_stream: 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 LightRAG MCP Server. Nothing to install.
query_text_stream 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 query_text_stream 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 query_text_stream. 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.
query_text_stream is provided by the LightRAG MCP Server MCP server (lalitsuryan/lightragmcp). 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 →