This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/list-reports.md
What list_reports does on Hospital Vuln Scanner
AI agents call list_reports 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_reports is rated Low
The tool merely lists or retrieves previously generated reports without modifying, deleting, or executing any operations. It is purely informational and non-destructive. In the context of a security scanning system, retrieving report metadata poses minimal risk—an agent could see what scans exist but cannot manipulate or delete them. This is consistent with the Read category for query and list operations.
From the tool's definition Tool name 'list_reports' and description '列出生成的报告' (list generated reports) indicate a data retrieval operation with no side effects. This is a query/list operation that retrieves existing report metadata.
Attacks that exploit this kind of access
The rule that runs list_reports 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_reports, this is the rule to start with:
list_reports 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_reports call is checked against it from then on.
Questions about list_reports
列出生成的报告. 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_reports: 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_reports 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_reports 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_reports. 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_reports 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