find_computers_in_protected_users
AI agents call find_computers_in_protected_users 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.
BloodHound MCP is designed for analyzing Active Directory attack paths through querying. This tool appears to query/enumerate computers associated with protected users—a read operation that retrieves security information without modifying or executing actions. The sibling tools are all reconnaissance queries against the BloodHound graph database.
From the tool's definition Tool name 'find_computers_in_protected_users' follows the pattern of sibling tools (find_all_domain_admins, find_asreproast_users, etc.) which are query/discovery functions.
Documented attack patterns abuse exactly the kind of access find_computers_in_protected_users 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_computers_in_protected_users:
{
"version": "1",
"default": "deny",
"tools": {
"find_computers_in_protected_users": {}
}
}find_computers_in_protected_users 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_computers_in_protected_users. 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_computers_in_protected_users: 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_computers_in_protected_users 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_computers_in_protected_users 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_computers_in_protected_users. 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_computers_in_protected_users 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.