discover_network
网络发现 - 扫描本地网络设备和医疗系统
This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/discover-network.md
What discover_network does on Hospital Vuln Scanner
AI agents invoke discover_network 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 discover_network is rated High
This tool performs active network discovery scanning, which constitutes an external operation that probes network devices and medical systems. In a hospital context, unauthorized or misconfigured network scanning can disrupt critical medical devices (e.g., infusion pumps, imaging systems), making misuse potentially dangerous.
From the tool's definition '扫描本地网络设备和医疗系统' (scan local network devices and medical systems) — actively probes and scans network infrastructure
Attacks that exploit this kind of access
The rule that runs discover_network 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 discover_network, this is the rule to start with:
discover_network 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 discover_network call is checked against it from then on.
Questions about discover_network
网络发现 - 扫描本地网络设备和医疗系统. 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 discover_network: 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.
discover_network 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 discover_network 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 discover_network. 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.
discover_network 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