AI agents use linkedin_posts_create to create or update resources in Linkedin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linkedin environment.
This tool creates new LinkedIn posts, which is a write operation that modifies data on the LinkedIn platform. While posts can be edited or deleted later (making it reversible), the tool can be misused by an AI agent to create unwanted, misleading, or spam posts at scale on behalf of a user, damaging reputation or violating platform policies.
From the tool's definition The tool name is 'linkedin_posts_create' and description states 'Create a new LinkedIn post using Posts API'. The verb 'create' directly indicates content creation with reversible effects.
Attacks that exploit this kind of access
Create a new LinkedIn post using Posts API. It is categorised as a Write tool in the Linkedin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linkedin MCP server in PolicyLayer and add a rule for linkedin_posts_create: 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. Nothing to install.
linkedin_posts_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the linkedin_posts_create 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.
Set action: deny in the PolicyLayer policy for linkedin_posts_create. 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.
linkedin_posts_create is provided by the Linkedin MCP server (maheidem/linkedin-optimizer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →