One-shot check: has theHarvester produced its JSON results yet?
AI agents call check_harvester_output to retrieve information from pentestMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that retrieves or queries the status/output of a previous operation. It is non-destructive, non-modifying, and poses minimal risk as it only checks for the existence and readiness of data produced by another tool. The blast radius if misused is negligible—an AI agent querying this repeatedly would at worst waste API calls or cause minor resource consumption.
From the tool's definition Tool name 'check_harvester_output' and description 'has theHarvester produced its JSON results yet?' indicate a polling/status check operation that queries whether a previous tool execution has completed and produced results.
Documented attack patterns abuse exactly the kind of access check_harvester_output gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_harvester_output:
{
"version": "1",
"default": "deny",
"tools": {
"check_harvester_output": {}
}
}check_harvester_output 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.
One-shot check: has theHarvester produced its JSON results yet?. It is categorised as a Read tool in the pentestMCP MCP Server, which means it retrieves data without modifying state.
Register the pentest MCP server in PolicyLayer and add a rule for check_harvester_output: 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 pentestMCP. Nothing to install.
check_harvester_output 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 check_harvester_output 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 check_harvester_output. 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.
check_harvester_output is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.