list_engagements
List all pentest engagements, optionally filtered by status.
This record as markdown: /tools/0xsteph-pentest-ai/list-engagements.md
What list_engagements does on Pentest Ai
AI agents call list_engagements to retrieve information from Pentest Ai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_engagements is rated Low
This tool retrieves and displays existing pentest engagement data without creating, modifying, deleting, or executing any operations. The filtering capability is a read-time parameter, not a modification action. The blast radius of misuse is limited to information disclosure about past or ongoing engagements, which is less severe than code execution or data destruction.
From the tool's definition Tool name 'list_engagements' and description 'List all pentest engagements, optionally filtered by status' indicate a query/retrieval operation with no mutation or side effects.
Attacks that exploit this kind of access
The rule that runs list_engagements safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_engagements, this is the rule to start with:
list_engagements is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pentest Ai, apply this rule, and every list_engagements call is checked against it from then on.
Questions about list_engagements
List all pentest engagements, optionally filtered by status. It is categorised as a Read tool in the Pentest Ai MCP Server, which means it retrieves data without modifying state.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for list_engagements: 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.
list_engagements 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_engagements 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_engagements. 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_engagements 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.
More on Pentest Ai, and thousands of servers like it.
This server
Across the catalogue