List all pentesting tools defined in the dataset schema with their categories and capabilities.
AI agents call list_tools 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 displays metadata about pentesting tools available in the dataset schema. It performs a read-only operation that returns information without modifying, executing, or deleting any data. The low severity reflects minimal blast radius—an AI agent listing tools cannot cause harm through this action alone.
From the tool's definition Tool name 'list_tools' and description 'List all pentesting tools defined in the dataset schema with their categories and capabilities' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_tools 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_tools:
{
"version": "1",
"default": "deny",
"tools": {
"list_tools": {}
}
}list_tools 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 pentesting tools defined in the dataset schema with their categories and capabilities. 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_tools: 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_tools 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_tools 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_tools. 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_tools 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.