AI agents use linkedin_ugc_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 user-generated content posts on LinkedIn. While the action is reversible (posts can be deleted or edited), it modifies the user's LinkedIn presence and could be misused to spam, impersonate, or post misleading content at scale. The medium severity reflects the reputational and potential ToS violation risks, but not financial impact or irreversibility.
From the tool's definition Tool name is 'linkedin_ugc_create' and description states 'Create UGC post'. The verb 'Create' indicates content is being generated and posted to LinkedIn, a reversible write operation.
Attacks that exploit this kind of access
Create UGC post (legacy API, mainly for video). 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_ugc_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_ugc_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_ugc_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_ugc_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_ugc_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 →