AI agents invoke execute_query to trigger actions in NebulaGraph 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.
The tool allows execution of arbitrary queries against a database. While the sibling tools (find_neighbors, find_path, get_space_schema, list_spaces) are Read operations, execute_query's permissive nature means it could execute CREATE, UPDATE, or DELETE statements depending on what query string is passed to it. This makes it Execute rather than Read.
From the tool's definition Tool name 'execute_query' combined with description 'Execute a query' indicates execution of arbitrary database queries.
Documented attack patterns abuse exactly the kind of access execute_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NebulaGraph MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_query": {
"limits": [
{
"counter": "execute_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_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.
Execute a query. It is categorised as a Execute tool in the NebulaGraph MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NebulaGraph MCP Server MCP server in PolicyLayer and add a rule for execute_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 NebulaGraph MCP Server. Nothing to install.
execute_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 execute_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 execute_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.
execute_query is provided by the NebulaGraph MCP Server MCP server (nebula-contrib/nebulagraph-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NebulaGraph 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.
5 NebulaGraph MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.