This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/get-vuln-stats.md
What get_vuln_stats does on Hospital Vuln Scanner
AI agents call get_vuln_stats 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 get_vuln_stats is rated Low
This tool retrieves and analyzes existing vulnerability statistics. It performs no write, destructive, execute, or financial operations. The function signature implies read-only access to aggregated vulnerability data, making it a Read category tool with low severity since it only provides information without side effects.
From the tool's definition Tool name 'get_vuln_stats' and description '漏洞统计分析' (vulnerability statistics analysis) indicate a query/retrieval operation that analyzes and returns vulnerability statistics without modifying any data.
Attacks that exploit this kind of access
The rule that runs get_vuln_stats 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 get_vuln_stats, this is the rule to start with:
get_vuln_stats 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 get_vuln_stats call is checked against it from then on.
Questions about get_vuln_stats
漏洞统计分析. 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 get_vuln_stats: 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.
get_vuln_stats 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 get_vuln_stats 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 get_vuln_stats. 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.
get_vuln_stats 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