New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

osint_get_results

Get paginated results from a previous OSINT search by search ID. Returns entries from a specific database and page.

SERVERRecon SOURCEdeltafantazulu/recon
Low RISK CLASS
Category Read
Parameters 30 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/deltafantazulu-recon/osint-get-results.md

What osint_get_results does on Recon

AI agents call osint_get_results 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.

ParameterTypeRequiredDescription
page number Page number (default: 1)
dbIndex number Database index (default: 0)
searchId string The search ID from a previous osint_search

Parameters from the server's own tool schema.

Why osint_get_results is rated Low

This tool retrieves and queries data from previous searches without modifying, creating, deleting, or executing operations. It is a Read operation. However, severity is rated 'high' rather than 'low' because the data being retrieved consists of sensitive personal information and leaked credentials from breach databases.

From the tool's definition Tool description states 'Get paginated results from a previous OSINT search by search ID. Returns entries from a specific database and page.' The verb 'Get' and 'Returns' indicate data retrieval with no modification.

Questions about osint_get_results

What does the osint_get_results tool do? +

Get paginated results from a previous OSINT search by search ID. Returns entries from a specific database and page. It is categorised as a Read tool in the Recon MCP Server, which means it retrieves data without modifying state.

What parameters does osint_get_results accept? +

osint_get_results accepts 3 parameters: page, dbIndex, searchId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on osint_get_results? +

Register the Recon MCP server in PolicyLayer and add a rule for osint_get_results: 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.

What risk level is osint_get_results? +

osint_get_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit osint_get_results? +

Yes. Add a rate_limit block to the osint_get_results 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.

How do I block osint_get_results completely? +

Set action: deny in the PolicyLayer policy for osint_get_results. 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.

What MCP server provides osint_get_results? +

osint_get_results 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Recon's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.