Low Risk

list_domain_computers

List domain computer(s)

How to control list_domain_computers ↓

AI agents call list_domain_computers 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.

Low Risk

This tool queries Active Directory to retrieve a list of computers in the domain. It performs read-only enumeration without creating, modifying, deleting, or executing any operations. While the BloodHound context suggests this is used for security analysis (which could inform attack paths), the tool itself is purely informational.

From the tool's definition Tool name 'list_domain_computers' and description 'List domain computer(s)' indicate enumeration of existing directory objects. The verb 'list' is a retrieval operation with no side effects or data modification.

Documented attack patterns abuse exactly the kind of access list_domain_computers 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 list_domain_computers:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_domain_computers": {}
  }
}

list_domain_computers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BloodHound MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_domain_computers tool do? +

List domain computer(s). It is categorised as a Read tool in the BloodHound MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_domain_computers? +

Register the BloodHound MCP server in PolicyLayer and add a rule for list_domain_computers: 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.

What risk level is list_domain_computers? +

list_domain_computers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_domain_computers? +

Yes. Add a rate_limit block to the list_domain_computers 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.

How do I block list_domain_computers completely? +

Set action: deny in the PolicyLayer policy for list_domain_computers. 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.

What MCP server provides list_domain_computers? +

list_domain_computers 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.

Enforce policy on every BloodHound MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.