check_neo4j

Check Neo4j graph database availability via the HTTP API. GET / returns server version and available endpoints. Port 7474 = HTTP, 7473 = HTTPS, 7687 = Bolt (use port_check for Bolt).

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-neo4j.md

WHAT IT DOES

What check_neo4j does on Mcp Nettools

AI agents call check_neo4j to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_neo4j is rated Low

This tool performs a diagnostic health check on a Neo4j instance by querying the HTTP API to retrieve version and endpoint information. It is a read-only operation that has no side effects, data modifications, or destructive capabilities. The tool belongs in the 'Read' category as it retrieves or queries data only.

From the tool's definition Tool description states 'Check Neo4j graph database availability via the HTTP API' and 'GET / returns server version and available endpoints' - these are read-only queries that retrieve information about server status and version without modifying data or…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_neo4j safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_neo4j, this is the rule to start with:

check_neo4j Allowed

check_neo4j is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_neo4j": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_neo4j call is checked against it from then on.

FAQ

Questions about check_neo4j

What does the check_neo4j tool do? +

Check Neo4j graph database availability via the HTTP API. GET / returns server version and available endpoints. Port 7474 = HTTP, 7473 = HTTPS, 7687 = Bolt (use port_check for Bolt). It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_neo4j? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_neo4j: 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 Mcp Nettools. Nothing to install.

What risk level is check_neo4j? +

check_neo4j is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_neo4j? +

Yes. Add a rate_limit block to the check_neo4j 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.

How do I block check_neo4j completely? +

Set action: deny in the PolicyLayer policy for check_neo4j. 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.

What MCP server provides check_neo4j? +

check_neo4j is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →