project_graph_cypher · Neo4j Gds MCP: Risk & Policy

WHAT IT DOES

What project_graph_cypher does on Neo4j Gds

AI agents invoke project_graph_cypher 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 project_graph_cypher needs a policy

The tool name suggests it projects a graph using a Cypher query into Neo4j GDS (Graph Data Science) catalog. Projecting a graph via Cypher involves executing a query against the database, which is an Execute-category action. The description is empty, reducing confidence, but the naming convention and server context (running graph algorithms on Neo4j) strongly imply Cypher execution.

From the tool's definition Tool name 'project_graph_cypher' implies executing a Cypher query to project a graph into the GDS graph catalog; sibling tools on this server all execute graph algorithms on a Neo4j database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

project_graph_cypher Rate-limited

project_graph_cypher 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": {
    "project_graph_cypher": {
      "limits": [
        {
          "counter": "project_graph_cypher_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 project_graph_cypher

What does the project_graph_cypher tool do? +

project_graph_cypher. 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 project_graph_cypher? +

Register the Neo4j Gds MCP server in PolicyLayer and add a rule for project_graph_cypher: 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 project_graph_cypher? +

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

Can I rate-limit project_graph_cypher? +

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

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

project_graph_cypher 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.