Search for public profiles linked to a username across social networks
AI agents call username_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.
username_recon performs reconnaissance by searching and retrieving publicly available profile information. This is a passive read operation that gathers data without side effects. While OSINT can support adversarial activities, the tool itself only queries public data sources and does not execute code, modify data, or cause destructive actions.
From the tool's definition Tool description states: 'Search for public profiles linked to a username across social networks' — a query/search operation that retrieves existing public data with no modifications, deletions, or execution of arbitrary commands.
Attacks that exploit this kind of access
Search for public profiles linked to a username across social networks. 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 username_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.
username_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 username_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 username_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.
username_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 →