Get discovered attack chains for an engagement. Shows how individual findings chain together into full compromise paths.
AI agents call get_attack_chains 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 performs information retrieval only. It presents attack chain data that has already been discovered during a pentest engagement, allowing review of compromise paths. There are no side effects, no code execution, no data modification or deletion. The blast radius of misuse is minimal—worst case an authorized user sees attack chain information they already have access to. Classified as Read with low severity.
From the tool's definition Tool retrieves and displays already-discovered attack chains without modifying, executing, or deleting any data. The description states 'Get discovered attack chains' and 'Shows how... findings chain together' — clear read operations that query results.
Documented attack patterns abuse exactly the kind of access get_attack_chains 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_attack_chains:
{
"version": "1",
"default": "deny",
"tools": {
"get_attack_chains": {}
}
}get_attack_chains 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 discovered attack chains for an engagement. Shows how individual findings chain together into full compromise paths. 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_attack_chains: 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_attack_chains 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_attack_chains 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_attack_chains. 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_attack_chains 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.