Run registered health checks and return component status.
AI agents call health_check to retrieve information from Graph Rag Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health checks are informational queries that retrieve system state. They have no side effects, do not modify data, do not execute arbitrary code, and do not destroy or move resources. The blast radius of misuse is minimal—an agent could only consume resources by repeated calls, but cannot cause damage through the operation itself.
From the tool's definition Tool name is 'health_check' and description states it 'Run registered health checks and return component status' — this is a diagnostic read operation that queries the status of system components without modifying, executing against external systems, or…
Attacks that exploit this kind of access
Run registered health checks and return component status. It is categorised as a Read tool in the Graph Rag Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Graph Rag Obsidian MCP server in PolicyLayer and add a rule for health_check: 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 Graph Rag Obsidian. Nothing to install.
health_check 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 health_check 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 health_check. 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.
health_check is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-mcp-server). 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 →