Low Risk

route_own_en_usrs_unconst_del

route_own_en_usrs_unconst_del

How to control route_own_en_usrs_unconst_del ↓

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

While the name suggests querying for users with unconstrained delegation (a privilege escalation vector commonly used in BloodHound analysis), the tool itself performs reconnaissance/analysis rather than active exploitation. All sibling tools on this server are Read category—they enumerate and analyze AD security posture.

From the tool's definition Tool name 'route_own_en_usrs_unconst_del' appears to parse as routing/querying owned enabled users with unconstrained delegation. The description is empty, making classification uncertain.

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

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

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

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

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

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

Can I rate-limit route_own_en_usrs_unconst_del? +

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

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

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