Get the processing pipeline status
AI agents call get_pipeline_status 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 current state information about a processing pipeline. The verb 'Get' and the read-only nature of status queries classify this as a Read operation with low severity since it neither modifies data nor triggers external operations. The blast radius is minimal as misuse would only expose non-sensitive operational metadata.
From the tool's definition Tool name 'get_pipeline_status' and description 'Get the processing pipeline status' indicate a query/retrieval operation that returns status information without modifying data or triggering side effects.
Attacks that exploit this kind of access
Get the processing pipeline status. 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 get_pipeline_status: 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.
get_pipeline_status 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 get_pipeline_status 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 get_pipeline_status. 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.
get_pipeline_status 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 →