scan_host_ports
A execute tool on the Hospital Vuln Scanner MCP server.
This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/scan-host-ports.md
What scan_host_ports does on Hospital Vuln Scanner
AI agents invoke scan_host_ports to trigger actions in Hospital Vuln Scanner. 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.
Why scan_host_ports is rated High
Port scanning is an active network operation that sends packets to remote systems. It is neither purely read (it triggers external effects on target systems) nor destructive, but it executes network reconnaissance. In a hospital/medical context, scanning live medical devices (e.g., infusion pumps, imaging systems) could disrupt critical care equipment, making misuse high severity.
From the tool's definition Tool name 'scan_host_ports' on a server described as supporting 'port scanning, vulnerability detection, medical system identification' — implies active network scanning against a target host.
Attacks that exploit this kind of access
The rule that runs scan_host_ports safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hospital Vuln Scanner, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_host_ports, this is the rule to start with:
scan_host_ports stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hospital Vuln Scanner, apply this rule, and every scan_host_ports call is checked against it from then on.
Questions about scan_host_ports
scan_host_ports is a execute tool on the Hospital Vuln Scanner MCP server. It is categorised as a Execute tool in the Hospital Vuln Scanner MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hospital Vuln Scanner MCP server in PolicyLayer and add a rule for scan_host_ports: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Hospital Vuln Scanner. Nothing to install.
scan_host_ports is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scan_host_ports rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for scan_host_ports. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
scan_host_ports is provided by the Hospital Vuln Scanner MCP server (12211725-star/hospital-vuln-scanner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hospital Vuln Scanner, and thousands of servers like it.
Across the catalogue