Retrieve evidence artifacts for an engagement or specific finding. Always returns the on-disk SHA-256 per artifact so callers can compare it against the hash stored in a finding's evidence_artifacts field to detect tampering. Args: include_content: read each artifact's file contents into content....
AI agents call get_evidence 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 returns artifacts and their metadata (SHA-256 hashes, file contents, HTTP exchange details) without modifying, executing, or deleting anything. It is purely a data retrieval operation. The inclusion of content and parsing of existing captured data does not constitute execution of new operations or commands.
From the tool's definition Tool description states 'Retrieve evidence artifacts' and 'read each artifact's file contents into `content`'.
Documented attack patterns abuse exactly the kind of access get_evidence 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_evidence:
{
"version": "1",
"default": "deny",
"tools": {
"get_evidence": {}
}
}get_evidence 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.
Retrieve evidence artifacts for an engagement or specific finding. Always returns the on-disk SHA-256 per artifact so callers can compare it against the hash stored in a finding's evidence_artifacts field to detect tampering. Args: include_content: read each artifact's file contents into content. as_curl: for http_request artifacts, parse the captured exchange and emit a copy-pasteable curl one-liner in curl. 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_evidence: 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_evidence 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_evidence 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_evidence. 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_evidence 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.