Search for people/leads on LinkedIn using keywords, title, company, seniority, geography, and industry filters. Uses the standard LinkedIn REST API (no SNAP partnership required). Works with any LinkedIn developer token that has the appropriate OAuth scopes. Note: The standard LinkedIn API has mo...
AI agents call linkedin_search_leads to retrieve information from Sales Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries LinkedIn profile data without creating, modifying, deleting, or executing operations. It is purely informational retrieval with no side effects. Severity is low because lead search results are non-sensitive business intelligence commonly available through standard LinkedIn usage, and misuse would not cause data loss, financial harm, or system damage.
From the tool's definition Tool performs 'Search for people/leads' with filters like 'keywords, title, company, seniority, geography, and industry'. The description states it 'Works with any LinkedIn developer token' for querying profile data.
Attacks that exploit this kind of access
Search for people/leads on LinkedIn using keywords, title, company, seniority, geography, and industry filters. Uses the standard LinkedIn REST API (no SNAP partnership required). Works with any LinkedIn developer token that has the appropriate OAuth scopes. Note: The standard LinkedIn API has more limited people search than Sales Navigator. For deep lead research, combine with ZoomInfo or Clay enrichment tools. Args: - keywords (string, optional): Free-text search across profiles - first_name / last_name (string, optional): Name filters - title (string, optional): Job title filter - company_name (string, optional): Current company - industry (string, optional): Industry - geography (string, optional): Location/region - seniority (string, optional):. It is categorised as a Read tool in the Sales Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Sales Intelligence MCP server in PolicyLayer and add a rule for linkedin_search_leads: 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 Sales Intelligence. Nothing to install.
linkedin_search_leads 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 linkedin_search_leads 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 linkedin_search_leads. 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.
linkedin_search_leads is provided by the Sales Intelligence MCP server (jbalbu01/sales-intelligence-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 →