generate_security_report · MCP Security Scanner MCP

WHAT IT DOES

What generate_security_report does on MCP Security Scanner

AI agents use generate_security_report to create or update resources in MCP Security Scanner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Security Scanner environment.

WHY IT NEEDS A POLICY

Why generate_security_report needs a policy

The tool generates and saves a security report file. While it reads scan results and aggregates them, its primary action is writing a Markdown file to storage. This is a Write operation (creating a new file). Severity is medium because the tool writes to the filesystem and could overwrite existing reports, but it does not execute code or delete data.

From the tool's definition El reporte se guarda en formato Markdown — the report is saved to disk in Markdown format, creating/writing a file.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_security_report Rate-limited

generate_security_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_security_report": {
      "limits": [
        {
          "counter": "generate_security_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 MCP Security Scanner, so you can run agents against it safely.

FAQ

Questions about generate_security_report

What does the generate_security_report tool do? +

Genera un reporte completo de seguridad en español que incluye: vulnerabilidades en dependencias (npm audit), vulnerabilidades en código fuente y secrets expuestos. El reporte se guarda en formato Markdown con todas las vulnerabilidades priorizadas por severidad y soluciones recomendadas. It is categorised as a Write tool in the MCP Security 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_security_report? +

Register the MCP Security Scanner MCP server in PolicyLayer and add a rule for generate_security_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 MCP Security Scanner. Nothing to install.

What risk level is generate_security_report? +

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

Can I rate-limit generate_security_report? +

Yes. Add a rate_limit block to the generate_security_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_security_report completely? +

Set action: deny in the PolicyLayer policy for generate_security_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_security_report? +

generate_security_report is provided by the MCP Security Scanner MCP server (jmitac/mcp-security-scanner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.