Get document status counts
AI agents call get_document_status_counts 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 queries and returns document status information without creating, modifying, deleting, or executing operations. It is a simple read operation that retrieves aggregate counts of document statuses, presenting no side effects or risk of unintended state changes.
From the tool's definition Tool name 'get_document_status_counts' and description 'Get document status counts' indicate retrieval and aggregation of status metrics. The verb 'Get' and the read-only nature of status counting operations confirm no data modification or deletion occurs.
Attacks that exploit this kind of access
Get document status counts. 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_document_status_counts: 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_document_status_counts 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_document_status_counts 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_document_status_counts. 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_document_status_counts 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 →