AI agents call find_tier_zero_locations 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 retrieves or queries data about critical security infrastructure (Tier Zero assets) without modifying, deleting, or executing external operations. Despite the empty description reducing confidence slightly, the naming pattern and server context (BloodHound analysis) clearly indicate a Read operation.
From the tool's definition Tool name 'find_tier_zero_locations' indicates a query/search operation (find_*). Sibling tools on the server follow the pattern of finding/identifying security-sensitive principals and systems (domain admins, kerberoastable users, CA administrators, etc.).
Documented attack patterns abuse exactly the kind of access find_tier_zero_locations 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_tier_zero_locations:
{
"version": "1",
"default": "deny",
"tools": {
"find_tier_zero_locations": {}
}
}find_tier_zero_locations 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_tier_zero_locations. 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_tier_zero_locations: 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_tier_zero_locations 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_tier_zero_locations 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_tier_zero_locations. 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_tier_zero_locations 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.