Medium Risk

create_video_post

create_video_post

How to control create_video_post ↓

AI agents use create_video_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

This tool creates new content (a video post) on LinkedIn, which is a reversible write operation. It modifies the user's LinkedIn presence by adding new content. Severity is medium because misuse could result in reputational harm or spam, but the action can be deleted/removed. This is less severe than destructive operations (which cannot be undone) or financial actions, and more severe than pure reads.

From the tool's definition Tool name 'create_video_post' and server context describing 'content creation and scheduling' indicates the tool creates video posts on LinkedIn. The empty description limits confidence but the naming is clear.

Documented attack patterns abuse exactly the kind of access create_video_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_video_post:

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

create_video_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_video_post tool do? +

create_video_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_video_post? +

Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for create_video_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_video_post? +

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

Can I rate-limit create_video_post? +

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

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

create_video_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.