# run_recon

Start a reconnaissance scan against a target. Returns immediately with an engagement_id while the recon agent runs asynchronously. Poll get_engagement_status(engagement_id) for status and get_findings(engagement_id=...) for results. Depth levels: - passive: OSINT only, no direct interaction - standard: Passive + light active scanning - deep: Full active scanning including port scans, vuln scans

Agent View of the PolicyLayer registry record for `run_recon`. HTML page: https://policylayer.com/tools/0xsteph-pentest-ai/run-recon

## Facts

- Tool: `run_recon`
- 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": "run_recon",
    "arguments": {}
  }
}
```

## Why run_recon is rated High

run_recon initiates active security scanning operations whose effects depend on the target and depth argument provided. While not destructive or financial, it executes external tools and commands (port scanning, vulnerability scanning) that produce observable effects on target systems and network interactions. The 'deep' option explicitly performs 'full active scanning' making this clearly an Execute category tool.

From the tool's own definition: "Tool performs reconnaissance scanning with configurable depth levels including 'active scanning', 'port scans', and 'vuln scans' against targets. These are executable operations that interact with external systems and trigger security tools."

## Use case

AI agents invoke run_recon 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": {
    "run_recon": {
      "limits": [
        {
          "counter": "run_recon_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_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_active_directory` — Execute — https://policylayer.com/tools/0xsteph-pentest-ai/test-active-directory.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
