Find mobile number using LinkedIn profile URL.
AI agents call prospeo_find_mobile to retrieve information from Prospeo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an external API (Prospeo) to retrieve contact information (mobile numbers) based on a LinkedIn profile URL. It has no side effects—it only retrieves and returns data. This is a straightforward Read operation. Severity is low because exposure of such lookup capabilities poses minimal immediate risk; the tool cannot modify systems, execute arbitrary code, or cause financial harm.
From the tool's definition Tool 'prospeo_find_mobile' with description 'Find mobile number using LinkedIn profile URL' retrieves data without modifying or deleting anything. The verb 'find' indicates a query/lookup operation.
Attacks that exploit this kind of access
Find mobile number using LinkedIn profile URL. It is categorised as a Read tool in the Prospeo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prospeo MCP Server MCP server in PolicyLayer and add a rule for prospeo_find_mobile: 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 Prospeo MCP Server. Nothing to install.
prospeo_find_mobile 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 prospeo_find_mobile 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 prospeo_find_mobile. 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.
prospeo_find_mobile is provided by the Prospeo MCP Server MCP server (meerkats-ai/prospeo-mcp-server). 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 →