Generate vulnerability report
AI agents call report_vuln to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or synthesizes vulnerability information into a report format. The verb 'generate' in the context of reporting suggests producing output from existing data rather than executing code, modifying systems, or triggering external operations. No side effects or destructive actions are indicated.
From the tool's definition Tool name 'report_vuln' and description 'Generate vulnerability report' indicate data retrieval and report generation with no modification or execution of systems.
Attacks that exploit this kind of access
Generate vulnerability report. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for report_vuln: 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 Claude Flow. Nothing to install.
report_vuln 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 report_vuln 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 report_vuln. 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.
report_vuln is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.