List all available pentesting scenario templates with categories, difficulties, and tags.
AI agents call list_scenarios to retrieve information from OffensiveSET without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing scenario templates without modifying, executing, or destructively affecting any data. It is purely informational, returning metadata about available scenarios. While the server generates penetration testing datasets, this specific tool only queries/lists what exists, making it a Read operation with minimal security risk.
From the tool's definition Tool name 'list_scenarios' and description 'List all available pentesting scenario templates' indicate a retrieval operation with no side effects. The verb 'list' is characteristic of Read category tools.
Documented attack patterns abuse exactly the kind of access list_scenarios 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 list_scenarios:
{
"version": "1",
"default": "deny",
"tools": {
"list_scenarios": {}
}
}list_scenarios is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available pentesting scenario templates with categories, difficulties, and tags. It is categorised as a Read tool in the OffensiveSET MCP Server, which means it retrieves data without modifying state.
Register the OffensiveSET MCP server in PolicyLayer and add a rule for list_scenarios: 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.
list_scenarios 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 list_scenarios 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 list_scenarios. 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.
list_scenarios 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.