List Certificate Authority server(s) [Required: Certipy]
AI agents call list_certificate_authority_servers 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 performs reconnaissance by querying and listing CA servers, which is a read-only operation with no data modification, deletion, or code execution. However, severity is elevated to 'high' because CA server enumeration is a critical information-gathering step in ADCS (Active Directory Certificate Services) attack chains.
From the tool's definition Tool name 'list_certificate_authority_servers' and description 'List Certificate Authority server(s)' indicate a query/enumeration operation that retrieves information about Certificate Authority servers in an Active Directory environment.
Documented attack patterns abuse exactly the kind of access list_certificate_authority_servers 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 list_certificate_authority_servers:
{
"version": "1",
"default": "deny",
"tools": {
"list_certificate_authority_servers": {}
}
}list_certificate_authority_servers 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.
List Certificate Authority server(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 list_certificate_authority_servers: 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.
list_certificate_authority_servers 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 list_certificate_authority_servers 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 list_certificate_authority_servers. 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.
list_certificate_authority_servers 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.