Check if theHarvester is available and working on the Kali host.
AI agents call theharvester_check_status to retrieve information from theHarvester MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Status checks are diagnostic operations that simply query the current state of a service. This tool does not retrieve sensitive data, execute code, modify data, or perform irreversible actions. While the server provides OSINT reconnaissance capabilities (which have security implications), this specific tool is merely a health check and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name and description indicate a status check operation ('Check if theHarvester is available and working'). This is a query operation with no side effects—it retrieves system state information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check if theHarvester is available and working on the Kali host. It is categorised as a Read tool in the theHarvester MCP Server MCP Server, which means it retrieves data without modifying state.
Register the theHarvester MCP Server MCP server in PolicyLayer and add a rule for theharvester_check_status: 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 theHarvester MCP Server. Nothing to install.
theharvester_check_status 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_check_status 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_check_status. 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_check_status is provided by the theHarvester MCP Server MCP server (schwarztim/sec-theharvester-mcp). 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 →