AI agents call data_quality 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.
BloodHound tools primarily serve to query and analyze Active Directory data without modifying it. A 'data_quality' tool most likely reports statistics or validation results about the dataset. No side effects are apparent from the context. Confidence is moderate due to the empty description, but the server's stated purpose (query and analyze) and sibling tool patterns support a Read classification.
From the tool's definition Tool name 'data_quality' is a standard BloodHound query tool context; other sibling tools on this server (adcs_info, asset_groups, computer_info, domain_info, group_info) are all Read-category query tools that retrieve AD attack path data.
Documented attack patterns abuse exactly the kind of access data_quality 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 data_quality:
{
"version": "1",
"default": "deny",
"tools": {
"data_quality": {}
}
}data_quality 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.
data_quality. 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 data_quality: 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.
data_quality 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 data_quality 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 data_quality. 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.
data_quality 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.