Low Risk

find_computers_webclient_running

find_computers_webclient_running

How to control find_computers_webclient_running ↓

What find_computers_webclient_running does on BloodHound MCP

AI agents call find_computers_webclient_running 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

Why find_computers_webclient_running needs a policy

This tool retrieves information about WebClient service state across computers in Active Directory—a pure reconnaissance/read operation with no data modification. It fits the Read category (search/query).

From the tool's definition Tool name 'find_computers_webclient_running' indicates a search/discovery operation that queries for computers with WebClient service status.

Documented attack patterns abuse exactly the kind of access find_computers_webclient_running gives an agent:

How to control find_computers_webclient_running

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_webclient_running:

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

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

Related tools and policies

Go deeper

Questions about find_computers_webclient_running

What does the find_computers_webclient_running tool do? +

find_computers_webclient_running. 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 find_computers_webclient_running? +

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

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

Can I rate-limit find_computers_webclient_running? +

Yes. Add a rate_limit block to the find_computers_webclient_running 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 find_computers_webclient_running completely? +

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

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

Enforce policy on every BloodHound MCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.