list_all_principals_with_local_admin_permission
How to control list_all_principals_with_local_admin_permission ↓
AI agents call list_all_principals_with_local_admin_permission 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.
Although the description is empty (lowering confidence slightly), the tool name and server context clearly indicate this retrieves and lists security principals with local admin permissions in Active Directory. This is a read-only query operation.
From the tool's definition Tool name indicates 'list_all_principals' - a query/enumeration operation. Server context shows BloodHound is an Active Directory analysis tool that performs natural language queries.
Documented attack patterns abuse exactly the kind of access list_all_principals_with_local_admin_permission 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_all_principals_with_local_admin_permission:
{
"version": "1",
"default": "deny",
"tools": {
"list_all_principals_with_local_admin_permission": {}
}
}list_all_principals_with_local_admin_permission 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_all_principals_with_local_admin_permission. 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_all_principals_with_local_admin_permission: 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_all_principals_with_local_admin_permission 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_all_principals_with_local_admin_permission 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_all_principals_with_local_admin_permission. 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_all_principals_with_local_admin_permission 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.