check_entity_exists
Check if an entity exists in the knowledge graph
This record as markdown: /tools/desimpkins-daniel-lightrag-mcp/check-entity-exists.md
What check_entity_exists does on Daniel LightRAG MCP Server
AI agents call check_entity_exists to retrieve information from Daniel LightRAG MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_entity_exists is rated Low
This is a straightforward read operation that queries the knowledge graph to determine entity existence. It has no side effects, does not modify data, and does not execute arbitrary code. The low severity reflects minimal blast radius if misused—an agent could only perform reconnaissance on the knowledge graph structure without causing harm.
From the tool's definition Tool name 'check_entity_exists' and description 'Check if an entity exists in the knowledge graph' indicate a pure query operation that retrieves status information without modifying or deleting data.
Attacks that exploit this kind of access
The rule that runs check_entity_exists safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Daniel LightRAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_entity_exists, this is the rule to start with:
check_entity_exists is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Daniel LightRAG MCP Server, apply this rule, and every check_entity_exists call is checked against it from then on.
Questions about check_entity_exists
Check if an entity exists in the knowledge graph. It is categorised as a Read tool in the Daniel LightRAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Daniel LightRAG MCP Server MCP server in PolicyLayer and add a rule for check_entity_exists: 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 Daniel LightRAG MCP Server. Nothing to install.
check_entity_exists 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 check_entity_exists 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 check_entity_exists. 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.
check_entity_exists is provided by the Daniel LightRAG MCP Server MCP server (desimpkins/daniel-lightrag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Daniel LightRAG MCP Server, and thousands of servers like it.
This server
Across the catalogue