Executes the provided openCypher against the graph.
AI agents invoke run_opencypher_query to trigger actions in Amazon EKS 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 openCypher queries against a graph database. While openCypher queries can be read-only, the tool itself permits execution of any valid query, including those that modify graph data (CREATE, SET, DELETE operations in openCypher/Cypher are supported). An AI agent could maliciously craft queries to modify, corrupt, or exfiltrate data from the EKS graph.
From the tool's definition Tool description states 'Executes the provided openCypher against the graph' - the verb 'Executes' combined with 'query' against a graph database indicates this runs arbitrary code/queries whose side effects depend on the query arguments provided.
Documented attack patterns abuse exactly the kind of access run_opencypher_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_opencypher_query:
{
"version": "1",
"default": "deny",
"tools": {
"run_opencypher_query": {
"limits": [
{
"counter": "run_opencypher_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} run_opencypher_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.
Executes the provided openCypher against the graph. It is categorised as a Execute tool in the Amazon EKS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for run_opencypher_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 Amazon EKS MCP Server. Nothing to install.
run_opencypher_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 run_opencypher_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 run_opencypher_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.
run_opencypher_query is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon EKS MCP Server, 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.
805 Amazon EKS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.