Low Risk

get_recommended_jobs

Get job recommendations from LinkedIn.

How to control get_recommended_jobs ↓

What get_recommended_jobs does on LinkedIn Model Context Protocol (MCP) Server

AI agents call get_recommended_jobs to retrieve information from LinkedIn Model Context Protocol (MCP) Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_recommended_jobs needs a policy

This tool queries LinkedIn's recommendation engine to retrieve job suggestions for the user. It has no side effects on data (no creation, modification, or deletion) and does not execute code or trigger financial transactions. The blast radius of misuse is minimal - an agent could only retrieve potentially unwanted job recommendations, which causes no harm to the user's LinkedIn account or data integrity.

From the tool's definition Tool is described as "Get job recommendations from LinkedIn" - a retrieval operation that returns data without modifying, deleting, or executing external actions. The verb 'get' and 'recommendations' indicate a read-only query operation.

Documented attack patterns abuse exactly the kind of access get_recommended_jobs gives an agent:

How to control get_recommended_jobs

PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Model Context Protocol (MCP) Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_recommended_jobs:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_recommended_jobs": {}
  }
}

get_recommended_jobs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register LinkedIn Model Context Protocol (MCP) Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_recommended_jobs

What does the get_recommended_jobs tool do? +

Get job recommendations from LinkedIn. It is categorised as a Read tool in the LinkedIn Model Context Protocol (MCP) Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recommended_jobs? +

Register the LinkedIn Model Context Protocol (MCP) Server MCP server in PolicyLayer and add a rule for get_recommended_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 Model Context Protocol (MCP) Server. Nothing to install.

What risk level is get_recommended_jobs? +

get_recommended_jobs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recommended_jobs? +

Yes. Add a rate_limit block to the get_recommended_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.

How do I block get_recommended_jobs completely? +

Set action: deny in the PolicyLayer policy for get_recommended_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.

What MCP server provides get_recommended_jobs? +

get_recommended_jobs is provided by the LinkedIn Model Context Protocol (MCP) Server MCP server (rayyan9477/linkedin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LinkedIn Model Context Protocol (MCP) Server tool call.

Start from LinkedIn Model Context Protocol (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.

13 LinkedIn Model Context Protocol (MCP) Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.