# test_active_directory Run Active Directory security assessment. Includes: BloodHound enumeration, Kerberoasting, AS-REP roasting, privilege escalation paths, delegation attacks, and domain dominance. Recommended (secure): pass auth_profile = name of an ntlm profile created via pentest-ai auth profile add. The password is resolved server-side and never enters the MCP/LLM context. Deprecated (insecure, removed in 0.11): credentials dict literal. Agent View of the PolicyLayer registry record for `test_active_directory`. HTML page: https://policylayer.com/tools/0xsteph-pentest-ai/test-active-directory ## Facts - Tool: `test_active_directory` - Server: Pentest Ai (`0xsteph/pentest-ai`) — https://policylayer.com/tools/0xsteph-pentest-ai.md - Homepage: https://github.com/0xSteph/pentest-ai - Risk category: Execute (High risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "test_active_directory", "arguments": {} } } ``` ## Why test_active_directory is rated High This tool actively runs offensive security techniques against an Active Directory environment — including credential attacks (Kerberoasting, AS-REP roasting), graph-based attack path enumeration (BloodHound), and domain dominance techniques. These are live exploit/attack operations against real infrastructure. From the tool's own definition: "BloodHound enumeration, Kerberoasting, AS-REP roasting, privilege escalation paths, delegation attacks, and domain dominance" ## Use case AI agents invoke test_active_directory to trigger actions in Pentest Ai. 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Pentest Ai: ```json { "version": "1", "default": "deny", "tools": { "test_active_directory": { "limits": [ { "counter": "test_active_directory_rate", "window": "minute", "max": 10, "scope": "grant" } ] } } } ``` ## Other tools on Pentest Ai (50) - `kill_process` — Destructive — https://policylayer.com/tools/0xsteph-pentest-ai/kill-process.md - `authenticated_scan` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/authenticated-scan.md - `builtin_scan` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/builtin-scan.md - `ensure_tools_installed` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/ensure-tools-installed.md - `http_request` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/http-request.md - `plan_tools` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/plan-tools.md - `resume_engagement` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/resume-engagement.md - `run_probe` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/run-probe.md - `run_recon` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/run-recon.md - `run_tool` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/run-tool.md - `scan_dns_builtin` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/scan-dns-builtin.md - `scan_ports_builtin` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/scan-ports-builtin.md - `select_agent` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/select-agent.md - `start_campaign` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/start-campaign.md - `start_engagement` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/start-engagement.md - `test_api_security` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-api-security.md - `test_cloud` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-cloud.md - `test_credentials` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-credentials.md - `test_mobile` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-mobile.md - `test_privesc` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-privesc.md - `test_social_engineering` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-social-engineering.md - `test_vulnerabilities` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-vulnerabilities.md - `test_web_app` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-web-app.md - `test_wireless` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-wireless.md - `validate_finding` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/validate-finding.md - `browser_inspect` — Read — https://policylayer.com/tools/0xsteph-pentest-ai/browser-inspect.md - `discover_attack_chains` — Read — https://policylayer.com/tools/0xsteph-pentest-ai/discover-attack-chains.md - `get_attack_chains` — Read — https://policylayer.com/tools/0xsteph-pentest-ai/get-attack-chains.md - `get_campaign_summary` — Read — https://policylayer.com/tools/0xsteph-pentest-ai/get-campaign-summary.md - `get_config` — Read — https://policylayer.com/tools/0xsteph-pentest-ai/get-config.md - …and 20 more: https://policylayer.com/tools/0xsteph-pentest-ai.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xsteph-pentest-ai · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xsteph-pentest-ai