// SCAN REPORT

Hospital Vuln Scanner

14 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 30 Jun 2026

6 can modify or destroy data

8 read-only

14 tools total

Community server · catalogue entry checked 30/06/2026

How to control Hospital Vuln Scanner ↓

TOOL MAP

What Hospital Vuln Scanner exposes to your agents

Read (8) Write / Execute (5) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Hospital Vuln Scanner tools

Destructive · High cancel_scan 取消正在运行的扫描任务 Execute · High start_scan This tool triggers execution of security scans against medical information systems. Execute · High discover_network This tool performs active network discovery scanning, which constitutes an external operation that probes network devices and medical systems. Execute · High scan_host_ports Port scanning is an active network operation that sends packets to remote systems.

6 of Hospital Vuln Scanner's 14 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Hospital Vuln Scanner

PolicyLayer is an MCP gateway — it sits between your AI agents and Hospital Vuln Scanner, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "cancel_scan": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "generate_report": {
    "limits": [
      {
        "counter": "generate_report_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_scan_status": {
    "limits": [
      {
        "counter": "get_scan_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Hospital Vuln Scanner — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON HOSPITAL VULN SCANNER →

Instant setup, no code required.

FULL CATALOGUE

All 14 Hospital Vuln Scanner tools

DESTRUCTIVE 1 tools

Destructive cancel_scan 取消正在运行的扫描任务

EXECUTE 3 tools

Execute discover_network 网络发现 - 扫描本地网络设备和医疗系统 Execute scan_host_ports scan_host_ports Execute start_scan start_scan

WRITE 2 tools

Write generate_report generate_report Write update_vulnerability_status update_vulnerability_status

READ 8 tools

Read get_scan_status 查询扫描任务状态和结果 Read get_system_status 获取系统运行状态和扫描引擎信息 Read get_vuln_stats 漏洞统计分析 Read get_vulnerability 获取漏洞详细信息 Read identify_medical_systems identify_medical_systems Read list_reports 列出生成的报告 Read list_scans list_scans Read list_vulnerabilities list_vulnerabilities

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Hospital Vuln Scanner

Can an AI agent delete data through the Hospital Vuln Scanner MCP server? +

Yes. The Hospital Vuln Scanner server exposes 1 destructive tools including cancel_scan. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Hospital Vuln Scanner? +

The Hospital Vuln Scanner server has 2 write tools including generate_report, update_vulnerability_status. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Hospital Vuln Scanner.

How many tools does the Hospital Vuln Scanner MCP server expose? +

14 tools across 4 categories: Destructive, Execute, Read, Write. 8 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Hospital Vuln Scanner? +

Register the Hospital Vuln Scanner MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Hospital Vuln Scanner tool call.

Deterministic rules across all 14 Hospital Vuln Scanner tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON HOSPITAL VULN SCANNER →

Instant setup, no code required.

14 Hospital Vuln Scanner tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Hospital Vuln Scanner's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →