HITS · Neo4j Gds MCP: Risk & Policy

WHAT IT DOES

What HITS does on Neo4j Gds

AI agents invoke HITS to trigger actions in Neo4j Gds. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why HITS needs a policy

The server is designed to execute graph algorithms on Neo4j databases. HITS (Hyperlink-Induced Topic Search) is a well-known graph algorithm for computing hub and authority scores. Given the server's explicit purpose of executing graph algorithms, this tool almost certainly runs the HITS algorithm. Empty description lowers confidence, but the Execute category fits based on server context.

From the tool's definition Tool name is 'HITS' with empty description. Server description states it runs graph algorithms on Neo4j databases by 'selecting and executing appropriate parameterised graph algorithms'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

HITS Rate-limited

HITS stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "HITS": {
      "limits": [
        {
          "counter": "hits_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Neo4j Gds, so you can run agents against it safely.

FAQ

Questions about HITS

What does the HITS tool do? +

HITS. It is categorised as a Execute tool in the Neo4j Gds MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on HITS? +

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

What risk level is HITS? +

HITS is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit HITS? +

Yes. Add a rate_limit block to the HITS 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 HITS completely? +

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

HITS is provided by the Neo4j Gds MCP server (neo4j-contrib/gds-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.