# prowler_scan

A execute tool on the Pengstrike MCP server.

Agent View of the PolicyLayer registry record for `prowler_scan`. HTML page: https://policylayer.com/tools/pengstrike-mcp/prowler-scan

## Facts

- Tool: `prowler_scan`
- Server: Pengstrike (`wangqiongpeng/pengstrike-mcp`) — https://policylayer.com/tools/pengstrike-mcp.md
- Homepage: https://github.com/wangqiongpeng/pengstrike-mcp
- 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": "prowler_scan",
    "arguments": {}
  }
}
```

## Why prowler_scan is rated High

Prowler is a well-known open-source cloud security assessment tool that performs active scanning of cloud environments (AWS, GCP, Azure) for misconfigurations and vulnerabilities. Based on the tool name and the server context (IntelliRecon security recon console with sibling tools like amass_scan, ai_vulnerability_assessment), this tool likely triggers an active Prowler scan against a target cloud environment.

From the tool's own definition: "Tool name 'prowler_scan' on a security recon server; description is empty and uninformative."

## Use case

AI agents invoke prowler_scan to trigger actions in Pengstrike. 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 Pengstrike:

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

## Other tools on Pengstrike (162)

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