AI agents call search_linkedin_people to retrieve information from LinkedIn MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data about LinkedIn users without creating, modifying, or deleting anything. It is a straightforward read operation that has no adverse consequences if misused by an AI agent, as it merely returns search results. The low severity reflects minimal blast radius—the worst outcome would be enumerating user profiles, which is already publicly searchable on LinkedIn.
From the tool's definition Tool name is 'search_linkedin_people' with description 'Search for people on LinkedIn'. The verb 'search' indicates a query operation with no side effects or data modification.
Documented attack patterns abuse exactly the kind of access search_linkedin_people gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_linkedin_people:
{
"version": "1",
"default": "deny",
"tools": {
"search_linkedin_people": {}
}
}search_linkedin_people is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for people on LinkedIn. It is categorised as a Read tool in the LinkedIn MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for search_linkedin_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 LinkedIn MCP Server. Nothing to install.
search_linkedin_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 search_linkedin_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 search_linkedin_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.
search_linkedin_people is provided by the LinkedIn MCP Server MCP server (quinnjr/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 LinkedIn MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.