Advanced search of LinkedIn profiles with comprehensive filtering options. Search by work status (is_open_to_work for job seekers, is_hiring for recruiters), professional attributes (is_creator for content creators/influencers, is_headstarter_affiliated for Headstarter community members), geograp...
AI agents call search-linkedin-profiles to retrieve information from Headstarter LinkedIn Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though search-linkedin-profiles only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Advanced search of LinkedIn profiles with comprehensive filtering options. Search by work status (is_open_to_work for job seekers, is_hiring for recruiters), professional attributes (is_creator for content creators/influencers, is_headstarter_affiliated for Headstarter community members), geographic location (city/country with partial matching), company/school affiliations (current or recent), and experience levels (minimum full-time or internship counts). Returns profiles with complete professional information including contact details, work history, education, and current status. Perfect for talent sourcing, networking, recruitment, and business development. It is categorised as a Read tool in the Headstarter LinkedIn Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Headstarter LinkedIn Network MCP Server MCP server in PolicyLayer and add a rule for search-linkedin-profiles: 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 Headstarter LinkedIn Network MCP Server. Nothing to install.
search-linkedin-profiles 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-profiles 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-profiles. 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-profiles is provided by the Headstarter LinkedIn Network MCP Server MCP server (team-headstart/headstarter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.