linkedin_search_people
AI agents call linkedin_search_people to retrieve information from WWIDE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve and query data without modifying it, making this a Read-category tool. Severity is medium because searching LinkedIn people data could expose personal or professional information about individuals, and an agent with this capability could conduct reconnaissance, identify targets, or perform profiling.
From the tool's definition Tool name 'linkedin_search_people' indicates a search operation. Sibling tools like 'linkedin_search_companies', 'linkedin_get_profile', and 'linkedin_get_company' are all Read-category data retrieval functions.
Attacks that exploit this kind of access
linkedin_search_people. It is categorised as a Read tool in the WWIDE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WWIDE MCP Server MCP server in PolicyLayer and add a rule for linkedin_search_people: 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 WWIDE MCP Server. Nothing to install.
linkedin_search_people 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_people 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_people. 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_people is provided by the WWIDE MCP Server MCP server (kulvir88/salesforce-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 →