// SCAN REPORT

LinkedIn Poster

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

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

Last updated: 4 Jul 2026

3 can modify or destroy data

2 read-only

5 tools total

Community server · catalogue entry verified 04/07/2026

How to control LinkedIn Poster ↓

TOOL MAP

What LinkedIn Poster exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous LinkedIn Poster tools

Write · Medium approve_post This tool modifies data by transitioning a queued post to published status on LinkedIn, which is reversible (posts can be deleted). Write · High publish_post This tool creates and publishes user-generated content to LinkedIn, which is a Write operation (creates/modifies data reversibly). Write · Medium queue_post This tool creates and stores new content (a LinkedIn post) in a queue for future publication.

3 of LinkedIn Poster's 5 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 Poster

PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Poster, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "approve_post": {
    "limits": [
      {
        "counter": "approve_post_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "health": {
    "limits": [
      {
        "counter": "health_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 Poster — 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 POSTER →

Instant setup, no code required.

FULL CATALOGUE

All 5 LinkedIn Poster tools

WRITE 3 tools

Write approve_post Approve a queued post (simple human-in-the-loop gate). Write publish_post Publish an approved post now via LinkedIn Posts API. Write queue_post Queue a LinkedIn post for later publishing.

READ 2 tools

Read health Check server status and required env vars. Read list_queue List queued posts.

FAQ

Questions about LinkedIn Poster

How do I prevent bulk modifications through LinkedIn Poster? +

The LinkedIn Poster server has 3 write tools including approve_post, publish_post, queue_post. 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 Poster.

How many tools does the LinkedIn Poster MCP server expose? +

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

How do I enforce a policy on LinkedIn Poster? +

Register the LinkedIn Poster 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 Poster tool call.

Deterministic rules across all 5 LinkedIn Poster tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LINKEDIN POSTER →

Instant setup, no code required.

5 LinkedIn Poster tools catalogued and risk-classified — across an index of 43,000+ MCP servers.