Execute a write Cypher query on the neo4j database
AI agents invoke write-neo4j-cypher to trigger actions in Neo4j MCP Server. 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.
This tool executes arbitrary write Cypher queries against a Neo4j database. While categorized as 'write', it can execute arbitrary Cypher including MERGE, SET, DELETE, DETACH DELETE, and other destructive operations depending on the query provided. Since it can span both Write and Destructive operations based on arguments, and it executes arbitrary code against the database, Execute is the most appropriate category.
From the tool's definition "Execute a write Cypher query on the neo4j database"
Attacks that exploit this kind of access
Execute a write Cypher query on the neo4j database. It is categorised as a Execute tool in the Neo4j MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Neo4j MCP Server MCP server in PolicyLayer and add a rule for write-neo4j-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 MCP Server. Nothing to install.
write-neo4j-cypher is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the write-neo4j-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.
Set action: deny in the PolicyLayer policy for write-neo4j-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.
write-neo4j-cypher is provided by the Neo4j MCP Server MCP server (rebots-online/mcp-neo4j). 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 →