Quick connectivity test. Returns {"ok": true} if the DB connection works.
AI agents call health_check to retrieve information from Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The health_check tool performs only a diagnostic query to verify database connectivity. It has no side effects, does not retrieve meaningful data, does not modify anything, and does not execute user-controlled code. It is a read-only status probe with minimal blast radius if misused by an agent.
From the tool's definition Tool is described as a 'Quick connectivity test' that 'Returns {"ok": true} if the DB connection works.' This is a status check operation with no data retrieval, modification, or execution of arbitrary operations.
Attacks that exploit this kind of access
Quick connectivity test. Returns {"ok": true} if the DB connection works. It is categorised as a Read tool in the Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Database MCP Server 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 Database MCP Server. 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 Database MCP Server MCP server (vrushil1/database-mcp). 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 →