AI agents use linkedin_assets_upload 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.
Uploading media assets creates new data in LinkedIn and modifies the user's content library. This is reversible (assets can be deleted) and has no financial or destructive implications. However, it has medium severity because an AI agent could upload inappropriate, misleading, or confidential content that damages the user's professional reputation or violates LinkedIn's terms of service.
From the tool's definition Tool name 'upload' and description 'Upload media assets (images/videos)' indicate creation/modification of data on LinkedIn. This is a write operation that creates new media assets in the user's LinkedIn account.
Attacks that exploit this kind of access
Upload media assets (images/videos). 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_assets_upload: 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_assets_upload 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_assets_upload 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_assets_upload. 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_assets_upload 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 →