create_vulnerability_report
A write tool on the Pengstrike MCP server.
This record as markdown: /tools/pengstrike-mcp/create-vulnerability-report.md
What create_vulnerability_report does on Pengstrike
AI agents use create_vulnerability_report to create or update resources in Pengstrike, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pengstrike environment.
Why create_vulnerability_report is rated Medium
The tool creates/generates a vulnerability report, which is a reversible write action. While the context (security testing tools) is concerning, the tool itself writes data rather than executing arbitrary code, deleting data, or moving money.
From the tool's definition Tool name 'create_vulnerability_report' indicates creation of a report artifact. Description is empty, so classification relies on name and context: IntelliRecon is a security recon console with sibling tools focused on vulnerability assessment, payload…
Attacks that exploit this kind of access
The rule that runs create_vulnerability_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_vulnerability_report, this is the rule to start with:
create_vulnerability_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 Pengstrike, apply this rule, and every create_vulnerability_report call is checked against it from then on.
Questions about create_vulnerability_report
create_vulnerability_report is a write tool on the Pengstrike MCP server. It is categorised as a Write tool in the Pengstrike MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pengstrike MCP server in PolicyLayer and add a rule for create_vulnerability_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 Pengstrike. Nothing to install.
create_vulnerability_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 create_vulnerability_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 create_vulnerability_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.
create_vulnerability_report is provided by the Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pengstrike, and thousands of servers like it.
This server
Across the catalogue