# list_probes

List every registered web probe with its metadata. Use this to discover what bug classes ptai can test for. The LLM driving an engagement picks probes by name and calls run_probe. Filters: - bug_class: only return probes for this bug class (e.g. sqli, idor, ssti, race_condition). - requires_auth_only: only return probes that need a logged-in session (call set_engagement_auth first or pass auth_profile to run_probe).

Agent View of the PolicyLayer registry record for `list_probes`. HTML page: https://policylayer.com/tools/0xsteph-pentest-ai/list-probes

## Facts

- Tool: `list_probes`
- Server: Pentest Ai (`0xsteph/pentest-ai`) — https://policylayer.com/tools/0xsteph-pentest-ai.md
- Homepage: https://github.com/0xSteph/pentest-ai
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_probes",
    "arguments": {}
  }
}
```

## Why list_probes is rated Low

This tool performs read-only discovery of available probes and their metadata. It returns information to inform which probes to invoke later via run_probe, with no side effects, data modification, or execution of security tests. The description emphasizes it helps the LLM "discover what bug classes ptai can test for" — a pure query operation.

From the tool's own definition: "list_probes retrieves and queries metadata about registered web probes with optional filters; explicitly documented as 'List every registered web probe with its metadata' with filtering options for bug_class and requires_auth_only."

## Use case

AI agents call list_probes to retrieve information from Pentest Ai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Pentest Ai:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_probes": {}
  }
}
```

## 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_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
- …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