# rustscan_fast_scan

A execute tool on the Intellirecon Console MCP server.

Agent View of the PolicyLayer registry record for `rustscan_fast_scan`. HTML page: https://policylayer.com/tools/intellirecon-console/rustscan-fast-scan

## Facts

- Tool: `rustscan_fast_scan`
- Server: Intellirecon Console (`dokotela021/intellirecon-console`) — https://policylayer.com/tools/intellirecon-console.md
- Homepage: https://github.com/dokotela021/intellirecon-console
- 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": "rustscan_fast_scan",
    "arguments": {}
  }
}
```

## Why rustscan_fast_scan is rated High

RustScan is a network port scanning tool that executes active network scans against targets. Even without a description, the tool name strongly implies it runs RustScan to perform fast port scanning. This constitutes an Execute action with high blast radius, as it actively probes external systems.

From the tool's own definition: "Tool name 'rustscan_fast_scan' references RustScan, a well-known fast port scanner used in security reconnaissance. Server context is a security recon console with sibling tools for scanning, payloads, and vulnerability assessment."

## Use case

AI agents invoke rustscan_fast_scan to trigger actions in Intellirecon Console. 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 Intellirecon Console:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "rustscan_fast_scan": {
      "limits": [
        {
          "counter": "rustscan_fast_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Intellirecon Console (168)

- `clear_cache` — Destructive — https://policylayer.com/tools/intellirecon-console/clear-cache.md
- `delete_file` — Destructive — https://policylayer.com/tools/intellirecon-console/delete-file.md
- `advanced_payload_generation` — Execute — https://policylayer.com/tools/intellirecon-console/advanced-payload-generation.md
- `ai_generate_attack_suite` — Execute — https://policylayer.com/tools/intellirecon-console/ai-generate-attack-suite.md
- `ai_generate_payload` — Execute — https://policylayer.com/tools/intellirecon-console/ai-generate-payload.md
- `ai_reconnaissance_workflow` — Execute — https://policylayer.com/tools/intellirecon-console/ai-reconnaissance-workflow.md
- `ai_test_payload` — Execute — https://policylayer.com/tools/intellirecon-console/ai-test-payload.md
- `ai_vulnerability_assessment` — Execute — https://policylayer.com/tools/intellirecon-console/ai-vulnerability-assessment.md
- `amass_scan` — Execute — https://policylayer.com/tools/intellirecon-console/amass-scan.md
- `angr_symbolic_execution` — Execute — https://policylayer.com/tools/intellirecon-console/angr-symbolic-execution.md
- `api_fuzzer` — Execute — https://policylayer.com/tools/intellirecon-console/api-fuzzer.md
- `arjun_parameter_discovery` — Execute — https://policylayer.com/tools/intellirecon-console/arjun-parameter-discovery.md
- `arp_scan_discovery` — Execute — https://policylayer.com/tools/intellirecon-console/arp-scan-discovery.md
- `autorecon_comprehensive` — Execute — https://policylayer.com/tools/intellirecon-console/autorecon-comprehensive.md
- `autorecon_scan` — Execute — https://policylayer.com/tools/intellirecon-console/autorecon-scan.md
- `binwalk_analyze` — Execute — https://policylayer.com/tools/intellirecon-console/binwalk-analyze.md
- `browser_agent_inspect` — Execute — https://policylayer.com/tools/intellirecon-console/browser-agent-inspect.md
- `bugbounty_authentication_bypass_testing` — Execute — https://policylayer.com/tools/intellirecon-console/bugbounty-authentication-bypass-testing.md
- `bugbounty_business_logic_testing` — Execute — https://policylayer.com/tools/intellirecon-console/bugbounty-business-logic-testing.md
- `bugbounty_comprehensive_assessment` — Execute — https://policylayer.com/tools/intellirecon-console/bugbounty-comprehensive-assessment.md
- `bugbounty_file_upload_testing` — Execute — https://policylayer.com/tools/intellirecon-console/bugbounty-file-upload-testing.md
- `bugbounty_reconnaissance_workflow` — Execute — https://policylayer.com/tools/intellirecon-console/bugbounty-reconnaissance-workflow.md
- `burpsuite_alternative_scan` — Execute — https://policylayer.com/tools/intellirecon-console/burpsuite-alternative-scan.md
- `burpsuite_scan` — Execute — https://policylayer.com/tools/intellirecon-console/burpsuite-scan.md
- `checkov_iac_scan` — Execute — https://policylayer.com/tools/intellirecon-console/checkov-iac-scan.md
- `clair_vulnerability_scan` — Execute — https://policylayer.com/tools/intellirecon-console/clair-vulnerability-scan.md
- `comprehensive_api_audit` — Execute — https://policylayer.com/tools/intellirecon-console/comprehensive-api-audit.md
- `create_attack_chain_ai` — Execute — https://policylayer.com/tools/intellirecon-console/create-attack-chain-ai.md
- `dalfox_xss_scan` — Execute — https://policylayer.com/tools/intellirecon-console/dalfox-xss-scan.md
- `dirb_scan` — Execute — https://policylayer.com/tools/intellirecon-console/dirb-scan.md
- …and 138 more: https://policylayer.com/tools/intellirecon-console.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=intellirecon-console · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/intellirecon-console