Find enabled Certificate Template(s) [Required: Certipy]
AI agents call find_enabled_certificate_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 is a Read operation—it retrieves and queries data about enabled certificate templates in an Active Directory environment. However, the severity is high because certificate template enumeration is a critical reconnaissance step in Active Directory attacks (ESC1-ESC13 certificate-based privilege escalation attacks).
From the tool's definition The tool name "find_enabled_certificate_templates" and description indicate it queries for enabled certificate templates in Active Directory. It performs discovery/enumeration of certificate configurations without modifying or deleting any data.
Documented attack patterns abuse exactly the kind of access find_enabled_certificate_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_enabled_certificate_templates:
{
"version": "1",
"default": "deny",
"tools": {
"find_enabled_certificate_templates": {}
}
}find_enabled_certificate_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 enabled Certificate Template(s) [Required: Certipy]. 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_enabled_certificate_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_enabled_certificate_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_enabled_certificate_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_enabled_certificate_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_enabled_certificate_templates 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.
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.