Analyze HTTP headers of the target domain.
AI agents call analyze_http_headers to retrieve information from External Reconnaissance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and examines HTTP headers from a target domain's responses. It performs no side effects, does not modify data, execute arbitrary code, delete anything, or commit financial transactions. It is purely analytical/informational in nature, making it a Read category tool.
From the tool's definition Tool name 'analyze_http_headers' and description 'Analyze HTTP headers of the target domain' indicate data retrieval without modification. HTTP header analysis is a passive reconnaissance activity that queries and examines existing headers from HTTP responses.
Documented attack patterns abuse exactly the kind of access analyze_http_headers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and External Reconnaissance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_http_headers:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_http_headers": {}
}
}analyze_http_headers 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.
Analyze HTTP headers of the target domain. It is categorised as a Read tool in the External Reconnaissance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the External Reconnaissance MCP Server MCP server in PolicyLayer and add a rule for analyze_http_headers: 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 External Reconnaissance MCP Server. Nothing to install.
analyze_http_headers 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 analyze_http_headers 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 analyze_http_headers. 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.
analyze_http_headers is provided by the External Reconnaissance MCP Server MCP server (naebo/mcp-external-recon-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from External Reconnaissance MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 External Reconnaissance MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.