# list_vulnerabilities

A read tool on the Hospital Vuln Scanner MCP server.

Agent View of the PolicyLayer registry record for `list_vulnerabilities`. HTML page: https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/list-vulnerabilities

## Facts

- Tool: `list_vulnerabilities`
- Server: Hospital Vuln Scanner (`12211725-star/hospital-vuln-scanner-mcp`) — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp.md
- Homepage: https://github.com/12211725-star/hospital-vuln-scanner-mcp
- 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_vulnerabilities",
    "arguments": {}
  }
}
```

## Why list_vulnerabilities is rated Low

The tool's name and position in a scanning/reporting suite strongly indicate it retrieves vulnerability data without modifying systems. However, confidence is moderately reduced because the description is empty.

From the tool's own definition: "Tool name 'list_vulnerabilities' with no description provided. Based on naming convention alongside sibling tools like 'get_vulnerability', 'get_vuln_stats', and 'get_scan_status', this appears to be a data retrieval operation that queries and returns…"

## Use case

AI agents call list_vulnerabilities to retrieve information from Hospital Vuln Scanner 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 Hospital Vuln Scanner:

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

## Other tools on Hospital Vuln Scanner (13)

- `cancel_scan` — Destructive — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/cancel-scan.md
- `discover_network` — Execute — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/discover-network.md
- `scan_host_ports` — Execute — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/scan-host-ports.md
- `start_scan` — Execute — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/start-scan.md
- `get_scan_status` — Read — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/get-scan-status.md
- `get_system_status` — Read — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/get-system-status.md
- `get_vuln_stats` — Read — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/get-vuln-stats.md
- `get_vulnerability` — Read — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/get-vulnerability.md
- `identify_medical_systems` — Read — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/identify-medical-systems.md
- `list_reports` — Read — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/list-reports.md
- `list_scans` — Read — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/list-scans.md
- `generate_report` — Write — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/generate-report.md
- `update_vulnerability_status` — Write — https://policylayer.com/tools/12211725-star-hospital-vuln-scanner-mcp/update-vulnerability-status.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=12211725-star-hospital-vuln-scanner-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/12211725-star-hospital-vuln-scanner-mcp
