ad_bloodhound_collect
A execute tool on the Zebbern Kali MCP server.
This record as markdown: /tools/zebbern-zebbern-kali-mcp/ad-bloodhound-collect.md
What ad_bloodhound_collect does on Zebbern Kali MCP
AI agents invoke ad_bloodhound_collect to trigger actions in Zebbern Kali MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ad_bloodhound_collect is rated High
BloodHound collection involves actively running enumeration agents against Active Directory infrastructure to map attack paths, trust relationships, group memberships, and privilege escalation vectors. Even though it is primarily a Read/reconnaissance operation, it executes active probing against live AD infrastructure, which constitutes an Execute-category action.
From the tool's definition Tool name 'ad_bloodhound_collect' on a Kali Linux penetration testing MCP server alongside tools like ad_secretsdump, ad_kerberoast, and ad_password_spray.
Attacks that exploit this kind of access
The rule that runs ad_bloodhound_collect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zebbern Kali MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ad_bloodhound_collect, this is the rule to start with:
ad_bloodhound_collect stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zebbern Kali MCP, apply this rule, and every ad_bloodhound_collect call is checked against it from then on.
Questions about ad_bloodhound_collect
ad_bloodhound_collect is a execute tool on the Zebbern Kali MCP server. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for ad_bloodhound_collect: 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 Zebbern Kali MCP. Nothing to install.
ad_bloodhound_collect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ad_bloodhound_collect 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 ad_bloodhound_collect. 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.
ad_bloodhound_collect is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zebbern Kali, and thousands of servers like it.
Across the catalogue