Check LightRAG server health status
AI agents call get_health 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 is a diagnostic/monitoring tool that queries the server's health status and returns information. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or commands. It fits the 'Read' category as a safe status check operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_health' and description 'Check LightRAG server health status' indicate a read-only query operation that retrieves status information without modifying any data or triggering external operations.
Attacks that exploit this kind of access
Check LightRAG server health 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_health: 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_health 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_health 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_health. 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_health 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 →