Query GPO data from BloodHound. info_type options: info - general GPO properties and attributes computers - computers this GPO is applied to controllers - principals that can modify this GPO ous - OUs this GPO is linked to tier_zeros - tier-zero principals associated with this GPO users - users t...
AI agents call gpo_info to retrieve information from BloodHound MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries Group Policy Object data from BloodHound, including properties, relationships, and associated principals. It performs read-only operations with no side effects. Severity is medium because GPO data (especially controllers and tier_zeros) reveals sensitive attack path information about Active Directory environments that could be misused for lateral movement or privilege escalation planning.
From the tool's definition Query GPO data from BloodHound... info_type options: info, computers, controllers, ous, tier_zeros, users
Documented attack patterns abuse exactly the kind of access gpo_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BloodHound MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gpo_info:
{
"version": "1",
"default": "deny",
"tools": {
"gpo_info": {}
}
}gpo_info 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.
Query GPO data from BloodHound. info_type options: info - general GPO properties and attributes computers - computers this GPO is applied to controllers - principals that can modify this GPO ous - OUs this GPO is linked to tier_zeros - tier-zero principals associated with this GPO users - users this GPO is applied to args: gpo_id: BloodHound object ID of the GPO (required) info_type: what to retrieve (default: info) limit: Max Results (default 100, useful in large environments) skip: Pagination offset (default 0). It is categorised as a Read tool in the BloodHound MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BloodHound MCP Server MCP server in PolicyLayer and add a rule for gpo_info: 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 Server. Nothing to install.
gpo_info 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 gpo_info 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 gpo_info. 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.
gpo_info is provided by the BloodHound MCP Server MCP server (mwnickerson/bloodhound_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BloodHound MCP Server, 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.
13 BloodHound MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.