create_linkedin_post
AI agents use create_linkedin_post to create or update resources in LinkedIn MCP Pro Max — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn MCP Pro Max environment.
Creating posts on LinkedIn modifies user-facing content irreversibly in the sense that once published, it becomes part of the user's professional record and reaches an audience. However, it is reversible (posts can be deleted), so it falls under Write rather than Destructive.
From the tool's definition Tool name 'create_linkedin_post' combined with server description stating 'content posting' capability indicates the tool creates new content on LinkedIn. Empty description limits precision but naming is explicit.
Attacks that exploit this kind of access
create_linkedin_post. It is categorised as a Write tool in the LinkedIn MCP Pro Max MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LinkedIn MCP Pro Max MCP server in PolicyLayer and add a rule for create_linkedin_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 MCP Pro Max. Nothing to install.
create_linkedin_post 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 create_linkedin_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.
Set action: deny in the PolicyLayer policy for create_linkedin_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.
create_linkedin_post is provided by the LinkedIn MCP Pro Max MCP server (mdnaimul22/linkedin-mcp-pro-max). 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 →