osint_search
Search leaked databases for email addresses, phone numbers, usernames, domains, or other identifiers. Returns results from multiple databases with categorized information. Note: Large searches may take 4-5 seconds. Use lower limit values for faster responses.
This record as markdown: /tools/deltafantazulu-recon/osint-search.md
What osint_search does on Recon
AI agents call osint_search to retrieve information from Recon without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of results to return (default: 5000). Lower values = faster responses. Range: 100-9000 |
query | string | — | The search query (email, phone, username, domain, etc.) |
Parameters from the server's own tool schema.
Why osint_search is rated Low
This is fundamentally a read operation that queries leaked data repositories. While the tool accesses sensitive information (exposed email addresses, phone numbers, usernames, domains), it retrieves existing data without side effects.
From the tool's definition Tool performs 'search' and 'returns results from multiple databases' with 'targeted lookups and streamlined retrieval of findings.' No modification, deletion, or execution occurs.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs osint_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Recon, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For osint_search, this is the rule to start with:
osint_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Recon, apply this rule, and every osint_search call is checked against it from then on.
Questions about osint_search
Search leaked databases for email addresses, phone numbers, usernames, domains, or other identifiers. Returns results from multiple databases with categorized information. Note: Large searches may take 4-5 seconds. Use lower limit values for faster responses. It is categorised as a Read tool in the Recon MCP Server, which means it retrieves data without modifying state.
osint_search accepts 2 parameters: limit, query. The full parameter table on this page comes from the server's own tool schema.
Register the Recon MCP server in PolicyLayer and add a rule for osint_search: 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 Recon. Nothing to install.
osint_search 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 osint_search 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 osint_search. 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.
osint_search is provided by the Recon MCP server (deltafantazulu/recon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Recon, and thousands of servers like it.
This server
Across the catalogue