Generate a professional pentest report (asynchronous). Formats: markdown, html, pdf, json Includes executive summary, technical findings, attack chains, proof of concepts, remediation guidance, and detection rules. Returns immediately with status='running'. PDF generation in particular can take 3...
AI agents use generate_report to create or update resources in Pentest Ai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pentest Ai environment.
This tool creates a report file on disk in one of several formats. It generates/writes a new document but does not delete data, execute code against targets, or involve financial transactions. The blast radius of misuse is low — it produces a report file that can be reviewed or discarded.
From the tool's definition Generate a professional pentest report (asynchronous)... the underlying file lands at reports/pentest-<engagement_id>-<date>.<format>
Documented attack patterns abuse exactly the kind of access generate_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_report:
{
"version": "1",
"default": "deny",
"tools": {
"generate_report": {
"limits": [
{
"counter": "generate_report_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Generate a professional pentest report (asynchronous). Formats: markdown, html, pdf, json Includes executive summary, technical findings, attack chains, proof of concepts, remediation guidance, and detection rules. Returns immediately with status='running'. PDF generation in particular can take 30-60s; the underlying file lands at reports/pentest-<engagement_id>-<date>.<format>. Poll the file or call get_engagement_summary(engagement_id) once the report exists. It is categorised as a Write tool in the Pentest Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pentest Ai 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 Pentest Ai. 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 Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.