start_scan
A execute tool on the Hospital Vuln Scanner MCP server.
This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/start-scan.md
What start_scan does on Hospital Vuln Scanner
AI agents invoke start_scan 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 start_scan is rated High
This tool triggers execution of security scans against medical information systems. Security scanning tools execute external operations (port scanning, vulnerability probes) whose effects depend on configuration arguments and network topology. While not destructive per se, scans can impact system performance and the scanning activity itself is an executed operation on external targets.
From the tool's definition Tool named 'start_scan' on a 'security scanning MCP server' that supports 'port scanning, vulnerability detection' and related operations.
Attacks that exploit this kind of access
The rule that runs start_scan 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 start_scan, this is the rule to start with:
start_scan 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 start_scan call is checked against it from then on.
Questions about start_scan
start_scan 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 start_scan: 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.
start_scan 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 start_scan 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 start_scan. 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.
start_scan 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