Search LinkedIn job listings by title, location, and/or company. Returns a list of matching jobs with title, company, location, and URL.
AI agents call search_jobs 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 queries LinkedIn's job database and returns results without creating, modifying, deleting, or executing any operations. It is a straightforward search/retrieval function analogous to a GET request. No financial transactions, destructive actions, or external code execution are involved.
From the tool's definition Tool description explicitly states it 'Search[es] LinkedIn job listings' and 'Returns a list of matching jobs' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Search LinkedIn job listings by title, location, and/or company. Returns a list of matching jobs with title, company, location, and URL. 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_jobs: 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_jobs 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_jobs 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_jobs. 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_jobs is provided by the LinkedIn MCP Server MCP server (markswendsen-code/mcp-linkedin). 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 →