Execute SELECT queries against the LinkedIn Network table (hs_linkedin_network) with automatic LIMIT protection. Contains comprehensive LinkedIn profile data including: Personal info (id, urn, username, first_name, last_name, summary, headline), Work status (is_creator, is_open_to_work, is_hiring...
AI agents call linkedin-sql-query 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 linkedin-sql-query 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
Execute SELECT queries against the LinkedIn Network table (hs_linkedin_network) with automatic LIMIT protection. Contains comprehensive LinkedIn profile data including: Personal info (id, urn, username, first_name, last_name, summary, headline), Work status (is_creator, is_open_to_work, is_hiring, is_headstarter_affiliated), Location (city, country), Experience counts (fulltime_count, internship_count), Recent company details (most_recent_company_name, most_recent_company_username, most_recent_company_title, most_recent_company_logo, most_recent_company_year), and Education info (most_recent_school, most_recent_school_degree, most_recent_school_month, most_recent_school_year). Only SELECT statements allowed for security. 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 linkedin-sql-query: 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.
linkedin-sql-query 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-sql-query 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-sql-query. 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-sql-query 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.