AI agents call find_ntlm_relay_edges to retrieve information from BloodHound MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries BloodHound to identify NTLM relay attack edges/paths within Active Directory infrastructure. While it retrieves security-sensitive information about exploitable relay conditions (which could inform malicious attacks), it performs no modifications, deletions, or execution of commands. It is fundamentally a read operation that queries the BloodHound database for attack path analysis.
From the tool's definition Tool name 'find_ntlm_relay_edges' combined with sibling tools like 'find_computers_outbound_ntlm_deny' and 'find_dcs_vulnerable_ntlm_relay' indicates discovery/query of NTLM relay attack paths in Active Directory.
Documented attack patterns abuse exactly the kind of access find_ntlm_relay_edges 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 find_ntlm_relay_edges:
{
"version": "1",
"default": "deny",
"tools": {
"find_ntlm_relay_edges": {}
}
}find_ntlm_relay_edges 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.
find_ntlm_relay_edges. It is categorised as a Read tool in the BloodHound MCP MCP Server, which means it retrieves data without modifying state.
Register the BloodHound MCP server in PolicyLayer and add a rule for find_ntlm_relay_edges: 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.
find_ntlm_relay_edges 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 find_ntlm_relay_edges 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 find_ntlm_relay_edges. 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.
find_ntlm_relay_edges is provided by the BloodHound MCP server (mordavid/bloodhound-mcp-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BloodHound MCP, 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.
75 BloodHound MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.