Get a summary of an engagement including finding counts, chains, and rules.
AI agents call get_engagement_summary to retrieve information from Pentest Ai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries engagement data (summary statistics, finding counts, chains, rules) with no side effects or irreversible actions. It fits the Read category—passive data retrieval used for reporting and analysis within a pentest workflow.
From the tool's definition Tool name uses 'get_' prefix and description states 'Get a summary' with query-like operations (counting findings, retrieving chains and rules). No modification, deletion, or execution of external operations described.
Documented attack patterns abuse exactly the kind of access get_engagement_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for get_engagement_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_engagement_summary": {}
}
}get_engagement_summary 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.
Get a summary of an engagement including finding counts, chains, and rules. 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 get_engagement_summary: 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.
get_engagement_summary 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 get_engagement_summary 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 get_engagement_summary. 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.
get_engagement_summary 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.
Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.