// SCAN REPORT

LinkedIn Model Context Protocol (MCP) Server

13 tools. 5 can modify or destroy data without limits.

5 write tools that can modify data. Rate limits recommended.

Last updated: 11 Jun 2026

5 can modify or destroy data

8 read-only

13 tools total

Community server · catalogue entry verified 11/06/2026

How to control LinkedIn Model Context Protocol (MCP) Server ↓

TOOL MAP

What LinkedIn Model Context Protocol (MCP) Server exposes to your agents

Read (8) Write / Execute (5) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous LinkedIn Model Context Protocol (MCP) Server tools

Write · Medium generate_cover_letter This tool creates new, reversible content (a cover letter document). Write · Medium generate_resume This is a Write operation because it creates a new document artifact (resume) that modifies the user's job application materials. Write · Medium tailor_resume This tool creates or modifies resume data (a new tailored version based on a job posting). Write · Medium update_application_status This tool creates or modifies data (application status) in a reversible manner—status changes can typically be undone by updating to a different status.

5 of LinkedIn Model Context Protocol (MCP) Server's 13 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control LinkedIn Model Context Protocol (MCP) Server

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. These are the rules we recommend:

Rate limit write operations

{
  "track_application": {
    "limits": [
      {
        "counter": "track_application_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_profile": {
    "limits": [
      {
        "counter": "analyze_profile_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register LinkedIn Model Context Protocol (MCP) Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LINKEDIN MODEL CONTEXT PROTOCOL (MCP) →

Free to start. No card required.

FULL CATALOGUE

All 13 LinkedIn Model Context Protocol (MCP) Server tools

WRITE 5 tools

Write track_application track_application Write generate_cover_letter Generate a personalized cover letter for a specific job posting. Write generate_resume Generate a professional resume from a LinkedIn profile using AI enhancement. Write tailor_resume Generate a resume tailored to a specific job posting. Write update_application_status Update the status of a tracked job application.

READ 8 tools

Read analyze_profile Analyze a LinkedIn profile using AI and provide optimization suggestions. Read get_company Get company information from LinkedIn. Read get_job_details Get detailed information about a specific LinkedIn job posting. Read get_profile Retrieve a LinkedIn profile including experience, education, and skills. Read get_recommended_jobs Get job recommendations from LinkedIn. Read list_applications List all tracked job applications, optionally filtered by status. Read list_templates List all available templates for resumes and cover letters. Read search_jobs search_jobs

FAQ

Questions about LinkedIn Model Context Protocol (MCP) Server

How do I prevent bulk modifications through LinkedIn Model Context Protocol (MCP) Server? +

The LinkedIn Model Context Protocol (MCP) Server server has 5 write tools including track_application, generate_cover_letter, generate_resume. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach LinkedIn Model Context Protocol (MCP) Server.

How many tools does the LinkedIn Model Context Protocol (MCP) Server MCP server expose? +

13 tools across 2 categories: Read, Write. 8 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on LinkedIn Model Context Protocol (MCP) Server? +

Register the LinkedIn Model Context Protocol (MCP) Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

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

Deterministic rules across all 13 LinkedIn Model Context Protocol (MCP) Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LINKEDIN MODEL CONTEXT PROTOCOL (MCP) →

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.