AI agents invoke cypher_query to trigger actions in Mcp Graph Engine. 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.
Cypher is the query language for graph databases (e.g., Neo4j). A 'cypher_query' tool likely executes arbitrary Cypher statements, which can include both read (MATCH) and write/destructive operations (CREATE, MERGE, DELETE, DROP).
From the tool's definition Tool name 'cypher_query' on a graph database server; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access cypher_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Graph Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for cypher_query:
{
"version": "1",
"default": "deny",
"tools": {
"cypher_query": {
"limits": [
{
"counter": "cypher_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} cypher_query 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.
Free to start. No card required.
cypher_query. It is categorised as a Execute tool in the Mcp Graph Engine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Graph Engine MCP server in PolicyLayer and add a rule for cypher_query: 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 Graph Engine. Nothing to install.
cypher_query 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 cypher_query 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 cypher_query. 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.
cypher_query is provided by the Mcp Graph Engine MCP server (utilitydelta/mcp-graph-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Graph Engine, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Mcp Graph Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.