generate_report
A write tool on the Hospital Vuln Scanner MCP server.
This record as markdown: /tools/12211725-star-hospital-vuln-scanner-mcp/generate-report.md
What generate_report does on Hospital Vuln Scanner
AI agents use generate_report to create or update resources in Hospital Vuln Scanner, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hospital Vuln Scanner environment.
Why generate_report is rated Medium
The tool appears to create or generate reports based on scan data and compliance information. This is a Write operation (creates new data artifacts) rather than Read (which would be retrieval only). It's not Execute because it doesn't run arbitrary code or commands - it generates structured reports from existing scan results.
From the tool's definition Tool name 'generate_report' combined with sibling tools like 'list_reports' and 'compliance report generation' mentioned in server description indicates report creation/generation functionality. No description provided to clarify exact behavior.
Attacks that exploit this kind of access
The rule that runs generate_report 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 generate_report, this is the rule to start with:
generate_report stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 generate_report call is checked against it from then on.
Questions about generate_report
generate_report is a write tool on the Hospital Vuln Scanner MCP server. It is categorised as a Write tool in the Hospital Vuln Scanner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hospital Vuln Scanner MCP server in PolicyLayer and add a rule for generate_report: 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.
generate_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_report 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 generate_report. 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.
generate_report 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