get_scan_status
查询扫描任务状态和结果
This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/get-scan-status.md
What get_scan_status does on Hospital Vuln Scanner
AI agents call get_scan_status 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_scan_status is rated Low
This tool retrieves or queries the status and results of security scans that have already been initiated. It does not create, modify, execute, delete, or move resources—it only reads and returns existing scan data.
From the tool's definition Tool name 'get_scan_status' and description '查询扫描任务状态和结果' (query scan task status and results) indicate retrieval of scan status information without side effects.
Attacks that exploit this kind of access
The rule that runs get_scan_status 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_scan_status, this is the rule to start with:
get_scan_status 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_scan_status call is checked against it from then on.
Questions about get_scan_status
查询扫描任务状态和结果. 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_scan_status: 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_scan_status 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_scan_status 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_scan_status. 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_scan_status 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