AI agents call graph_analysis to retrieve information from BloodHound MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Graph analysis in the context of BloodHound involves traversing and analyzing Active Directory relationships to understand attack paths. This is fundamentally a Read operation — it retrieves and analyzes existing data without creating, modifying, or deleting entities.
From the tool's definition BloodHound MCP Server is described as enabling professionals to 'query and analyze Active Directory attack paths' and sibling tools include 'cypher_query', 'domain_info', 'group_info', 'computer_info' — all read operations.
Documented attack patterns abuse exactly the kind of access graph_analysis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BloodHound MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for graph_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"graph_analysis": {}
}
}graph_analysis is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
graph_analysis. It is categorised as a Read tool in the BloodHound MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BloodHound MCP Server MCP server in PolicyLayer and add a rule for graph_analysis: 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 Server. Nothing to install.
graph_analysis is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the graph_analysis 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 graph_analysis. 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.
graph_analysis is provided by the BloodHound MCP Server MCP server (mwnickerson/bloodhound_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BloodHound 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.
13 BloodHound MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.