AI agents use linkedin_post_profile_update 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 modifies data on the LinkedIn platform. It is reversible (posts can be deleted or edited), so it falls under Write rather than Destructive. Severity is medium because misuse could result in unwanted posts to professional networks with reputational consequences, but the blast radius is limited to the user's own profile.
From the tool's definition Tool description states 'Create a post' which is a create action. The name contains 'post' and 'profile_update' indicating content creation. Server description confirms 'LinkedIn post creation' as a capability.
Attacks that exploit this kind of access
📢 Create a post announcing your profile updates. 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_post_profile_update: 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_post_profile_update 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_post_profile_update 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_post_profile_update. 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_post_profile_update 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 →