get_campaign_summary
Get aggregated summary across all engagements in a campaign.
This record as markdown: /tools/0xsteph-pentest-ai/get-campaign-summary.md
What get_campaign_summary does on Pentest Ai
AI agents call get_campaign_summary 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 get_campaign_summary is rated Low
This tool retrieves and aggregates existing data from completed engagements within a campaign. It performs no write operations, does not execute code or commands, does not delete data, and involves no financial transactions. The 'get' verb and 'summary' retrieval pattern are characteristic of Read operations.
From the tool's definition Tool name 'get_campaign_summary' and description 'Get aggregated summary across all engagements in a campaign' indicates a retrieval/query operation that aggregates and returns data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs get_campaign_summary 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 get_campaign_summary, this is the rule to start with:
get_campaign_summary 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 get_campaign_summary call is checked against it from then on.
Questions about get_campaign_summary
Get aggregated summary across all engagements in a campaign. 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_campaign_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_campaign_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_campaign_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_campaign_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_campaign_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.
More on Pentest Ai, and thousands of servers like it.
This server
Across the catalogue