generate_report · Hospital Vuln Scanner MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why generate_report needs a policy

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

Recommended rule Ready

Verdict

generate_report Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_report": {
      "limits": [
        {
          "counter": "generate_report_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hospital Vuln Scanner, so you can run agents against it safely.

FAQ

Questions about generate_report

What does the generate_report tool do? +

generate_report. 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.

How do I enforce a policy on generate_report? +

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.

What risk level is generate_report? +

generate_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_report? +

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.

How do I block generate_report completely? +

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.

What MCP server provides generate_report? +

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.