Generate an improved V2 offensive security dataset with unique outputs per entry, failure cases, deep thinking, and massive prompt diversity. Recommended over V1.
AI agents use generate_dataset_v2 to create or update resources in OffensiveSET — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OffensiveSET environment.
The tool creates/generates new offensive security datasets, which is a reversible write operation. While the datasets contain simulated pentesting scenarios and attack chains, the tool itself doesn't execute actual attacks or perform destructive actions—it generates synthetic training data.
From the tool's definition Tool generates and creates datasets ("Generate an improved V2 offensive security dataset"), which are new data artifacts.
Documented attack patterns abuse exactly the kind of access generate_dataset_v2 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OffensiveSET, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_dataset_v2:
{
"version": "1",
"default": "deny",
"tools": {
"generate_dataset_v2": {
"limits": [
{
"counter": "generate_dataset_v2_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_dataset_v2 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 an improved V2 offensive security dataset with unique outputs per entry, failure cases, deep thinking, and massive prompt diversity. Recommended over V1. It is categorised as a Write tool in the OffensiveSET MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OffensiveSET MCP server in PolicyLayer and add a rule for generate_dataset_v2: 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 OffensiveSET. Nothing to install.
generate_dataset_v2 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_dataset_v2 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_dataset_v2. 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_dataset_v2 is provided by the OffensiveSET MCP server (pentesterflow/offensiveset). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 OffensiveSET tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 OffensiveSET tools catalogued and risk-classified — across an index of 42,500+ MCP servers.