AI agents call find_esc2_vulnerable_templates 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.
This tool queries BloodHound's graph database to identify ESC2 (Encrypted Suspicion of Certificate Service 2) vulnerable certificate templates—a reconnaissance task with no write or destructive operations. It returns information for security analysis. Despite the security-sensitive nature of what it exposes (Active Directory vulnerabilities), the tool itself performs only read operations.
From the tool's definition Tool name is 'find_esc2_vulnerable_templates' with empty description. The 'find_' prefix and sibling tools (find_all_domain_admins, find_kerberoastable_users, find_asreproast_users, etc.) are all query/reconnaissance functions that retrieve security…
Documented attack patterns abuse exactly the kind of access find_esc2_vulnerable_templates 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_esc2_vulnerable_templates:
{
"version": "1",
"default": "deny",
"tools": {
"find_esc2_vulnerable_templates": {}
}
}find_esc2_vulnerable_templates 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_esc2_vulnerable_templates. 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_esc2_vulnerable_templates: 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_esc2_vulnerable_templates 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_esc2_vulnerable_templates 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_esc2_vulnerable_templates. 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_esc2_vulnerable_templates 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.