Passive OSINT reconnaissance for a domain: WHOIS, DNS, subdomains,
AI agents call domain_recon to retrieve information from MCP OSINT Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
domain_recon performs passive information gathering through standard DNS and WHOIS lookups. These are non-destructive read operations that query existing data with no side effects, no code execution, and no data modification. Even in a sandboxed environment, the tool's function is fundamentally a Read operation.
From the tool's definition Tool description states 'Passive OSINT reconnaissance' with operations including 'WHOIS, DNS, subdomains' — all read-only queries that retrieve publicly available information without modifying data or executing code.
Attacks that exploit this kind of access
Passive OSINT reconnaissance for a domain: WHOIS, DNS, subdomains,. It is categorised as a Read tool in the MCP OSINT Server MCP Server, which means it retrieves data without modifying state.
Register the MCP OSINT Server MCP server in PolicyLayer and add a rule for domain_recon: 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 OSINT Server. Nothing to install.
domain_recon 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_recon 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_recon. 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_recon is provided by the MCP OSINT Server MCP server (lliwi/osint-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 →