Check domain history and reputation indicators
AI agents call domain_history to retrieve information from MCP Recon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information and reputation data about domains without modifying, executing, or destroying anything. It is a reconnaissance/passive information gathering tool, consistent with the server's purpose of 'passive and active information gathering'. The action is read-only: inspecting existing records and indicators.
From the tool's definition Tool name 'domain_history' and description 'Check domain history and reputation indicators' indicate information retrieval with no side effects. The verb 'Check' and context of 'history' and 'reputation indicators' confirm passive data querying.
Documented attack patterns abuse exactly the kind of access domain_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Recon, and nothing reaches the server without passing your rules. This is the rule we recommend for domain_history:
{
"version": "1",
"default": "deny",
"tools": {
"domain_history": {}
}
}domain_history 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.
Check domain history and reputation indicators. It is categorised as a Read tool in the MCP Recon MCP Server, which means it retrieves data without modifying state.
Register the MCP Recon MCP server in PolicyLayer and add a rule for domain_history: 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 MCP Recon. Nothing to install.
domain_history 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 domain_history 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 domain_history. 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.
domain_history is provided by the MCP Recon MCP server (sundayz-hunter/mcp_recon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Recon, 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.
13 MCP Recon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.