Search for jobs on LinkedIn using a search term.
AI agents call search_jobs to retrieve information from MCP-LinkedIn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves job search results from LinkedIn based on user-provided search terms. It has no side effects, does not modify data, does not execute code, and does not commit financial transactions. It is purely informational retrieval, fitting the 'Read' category. Severity is low because misuse would only expose job listing information already publicly available on LinkedIn.
From the tool's definition Tool is named 'search_jobs' and described as 'Search for jobs on LinkedIn using a search term.' This is a query/retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Search for jobs on LinkedIn using a search term. It is categorised as a Read tool in the MCP-LinkedIn MCP Server, which means it retrieves data without modifying state.
Register the MCP-LinkedIn 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 MCP-LinkedIn. 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 MCP-LinkedIn MCP server (logos-parthenos-ai/linkedin-mcp-server). 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 →