Medium Risk

create_post

create_post

How to control create_post ↓

AI agents use create_post to create or update resources in LinkedIn Intelligence MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn Intelligence MCP Server environment.

Medium Risk

Creating posts on LinkedIn is a reversible Write operation—posts can be edited or deleted. It modifies data (user's content/profile) but does not permanently destroy data or execute arbitrary code. Severity is medium because misuse could result in unwanted public statements, reputational harm, or spam, but the effects are recoverable and scoped to the user's own account by default.

From the tool's definition Tool name 'create_post' combined with server context describing 'content creation and scheduling' indicates the tool creates new posts on LinkedIn. The sibling tool 'cancel_scheduled_post' confirms this server manages post lifecycle operations.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_post:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_post": {
      "limits": [
        {
          "counter": "create_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_post stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register LinkedIn Intelligence 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the create_post tool do? +

create_post. It is categorised as a Write tool in the LinkedIn Intelligence MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_post? +

Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for create_post: 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 Intelligence MCP Server. Nothing to install.

What risk level is create_post? +

create_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_post? +

Yes. Add a rate_limit block to the create_post 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 create_post completely? +

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

create_post is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/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 Intelligence MCP Server tool call.

Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.