theharvester_scan
AI agents call theharvester_scan to retrieve information from Kali Linux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
TheHarvester passively gathers publicly available information about targets (emails, subdomains, etc.) through queries to public sources. It performs reconnaissance and information retrieval (Read category) with no side effects on target systems. Severity is medium because reconnaissance enables further attacks, but the tool itself is purely informational.
From the tool's definition Tool name 'theharvester_scan' indicates a scanning operation. TheHarvester is a well-known OSINT (Open Source Intelligence) tool that performs email and subdomain enumeration without modifying target systems.
Attacks that exploit this kind of access
theharvester_scan. It is categorised as a Read tool in the Kali Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for theharvester_scan: 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 Kali Linux MCP Server. Nothing to install.
theharvester_scan 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 theharvester_scan 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 theharvester_scan. 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.
theharvester_scan is provided by the Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →