Low Risk

find_all_enabled_kerberoastable_users

Find all enabled kerberoastable user(s)

How to control find_all_enabled_kerberoastable_users ↓

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

Low Risk

This tool queries and lists Active Directory users matching specific vulnerability criteria (Kerberoastable accounts). While it performs reconnaissance that could enable attack preparation, the tool itself only reads/retrieves data without modifying or executing anything.

From the tool's definition Tool name 'find_all_enabled_kerberoastable_users' and description 'Find all enabled kerberoastable user(s)' indicate a query/search operation that retrieves information about vulnerable users in Active Directory.

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

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

find_all_enabled_kerberoastable_users 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 find_all_enabled_kerberoastable_users tool do? +

Find all enabled kerberoastable user(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 find_all_enabled_kerberoastable_users? +

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

What risk level is find_all_enabled_kerberoastable_users? +

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

Can I rate-limit find_all_enabled_kerberoastable_users? +

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

How do I block find_all_enabled_kerberoastable_users completely? +

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

What MCP server provides find_all_enabled_kerberoastable_users? +

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