Update an existing position on your LinkedIn profile
AI agents use update_linkedin_position to create or update resources in LinkedIn MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn MCP Server environment.
This tool modifies (rather than deletes) existing profile information reversibly. A user or admin can correct the data afterward. While it affects professional reputation and visibility, it does not irreversibly destroy data, execute arbitrary code, or move money.
From the tool's definition Tool name contains 'update' and description states 'Update an existing position on your LinkedIn profile', indicating modification of existing data.
Documented attack patterns abuse exactly the kind of access update_linkedin_position gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_linkedin_position:
{
"version": "1",
"default": "deny",
"tools": {
"update_linkedin_position": {
"limits": [
{
"counter": "update_linkedin_position_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_linkedin_position stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing position on your LinkedIn profile. It is categorised as a Write tool in the LinkedIn MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for update_linkedin_position: 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 Server. Nothing to install.
update_linkedin_position 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 update_linkedin_position 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 update_linkedin_position. 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.
update_linkedin_position is provided by the LinkedIn MCP Server MCP server (quinnjr/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 LinkedIn MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.