執行Cypher查詢並返回結果 Args: query: Cypher查詢字符串 parameters: 查詢參數字典 Returns: 查詢結果列表
AI agents invoke run_query to trigger actions in BloodHound MCP. 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 is Execute category because it runs arbitrary code (Cypher queries) against a live Active Directory environment whose effects depend entirely on the query arguments provided by an AI agent. An agent with access to this tool could enumerate domain credentials, discover privilege escalation paths, identify compromised accounts, or query sensitive security configurations.
From the tool's definition Tool executes arbitrary Cypher queries against Active Directory graph database with user-supplied query strings and parameters. Description states '執行Cypher查詢並返回結果' (Execute Cypher query and return results).
Documented attack patterns abuse exactly the kind of access run_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BloodHound MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_query:
{
"version": "1",
"default": "deny",
"tools": {
"run_query": {
"limits": [
{
"counter": "run_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_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查詢並返回結果 Args: query: Cypher查詢字符串 parameters: 查詢參數字典 Returns: 查詢結果列表. It is categorised as a Execute tool in the BloodHound MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BloodHound MCP server in PolicyLayer and add a rule for run_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 BloodHound MCP. Nothing to install.
run_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_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_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_query is provided by the BloodHound MCP server (stevenyu113228/bloodhound-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 BloodHound MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 BloodHound MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.