Find a phone number using LinkedIn profile URL.
AI agents call findyemail_find_phone to retrieve information from Findymail 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 service (Findymail API) to retrieve publicly available contact information (phone numbers) based on a LinkedIn profile URL. It is a read-only operation that retrieves data without creating, modifying, deleting, or executing any changes.
From the tool's definition Tool name 'findyemail_find_phone' and description 'Find a phone number using LinkedIn profile URL' indicate a lookup/retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Find a phone number using LinkedIn profile URL. It is categorised as a Read tool in the Findymail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Findymail MCP Server MCP server in PolicyLayer and add a rule for findyemail_find_phone: 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 Findymail MCP Server. Nothing to install.
findyemail_find_phone 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 findyemail_find_phone 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 findyemail_find_phone. 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.
findyemail_find_phone is provided by the Findymail MCP Server MCP server (meerkats-ai/findymail-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 →