Delete a position from your LinkedIn profile
AI agents call delete_linkedin_position to permanently remove resources in LinkedIn MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a position entry from a user's LinkedIn profile. Deletion of profile data is irreversible and constitutes a destructive action. An AI agent with access to this tool could maliciously erase entire career histories, causing reputational and professional harm.
From the tool's definition Tool name contains 'delete' and description states 'Delete a position from your LinkedIn profile' — irreversibly removes a career history entry that cannot be restored by the AI agent.
Documented attack patterns abuse exactly the kind of access delete_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 delete_linkedin_position:
{
"version": "1",
"default": "deny",
"hide": [
"delete_linkedin_position"
]
}delete_linkedin_position disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a position from your LinkedIn profile. It is categorised as a Destructive tool in the LinkedIn MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_linkedin_position is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.