list_scans
A read tool on the Hospital Vuln Scanner MCP server.
This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/list-scans.md
What list_scans does on Hospital Vuln Scanner
AI agents call list_scans 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.
Why list_scans is rated Low
The 'list_' prefix is a standard convention for retrieval operations that query and return data without modification. Context from sibling tools confirms this server provides scanning and reporting capabilities where 'list' operations would enumerate existing scans. No destructive, write, execute, or financial operations are indicated.
From the tool's definition Tool name 'list_scans' combined with sibling tools like 'list_reports' and 'list_vulnerabilities' suggests query/enumeration functionality. No description provided, but naming convention strongly implies data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs list_scans 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 list_scans, this is the rule to start with:
list_scans is read-only, so it stays allowed. 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 list_scans call is checked against it from then on.
Questions about list_scans
list_scans is a read tool on the Hospital Vuln Scanner MCP server. It is categorised as a Read tool in the Hospital Vuln Scanner MCP Server, which means it retrieves data without modifying state.
Register the Hospital Vuln Scanner MCP server in PolicyLayer and add a rule for list_scans: 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.
list_scans is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_scans 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 list_scans. 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.
list_scans 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.
This server
Across the catalogue