Delete a publication from your LinkedIn profile
AI agents call delete_linkedin_publication 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.
Deletion operations are irreversible and cannot be undone, making this Destructive rather than Write. The blast radius is high because an AI agent could remove important professional publications that took effort to add, damaging the user's professional profile visibility and credibility. However, it is scoped to a single publication rather than bulk profile destruction, preventing a critical rating.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a publication from your LinkedIn profile' - this irreversibly removes data from the user's LinkedIn profile.
Documented attack patterns abuse exactly the kind of access delete_linkedin_publication 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_publication:
{
"version": "1",
"default": "deny",
"hide": [
"delete_linkedin_publication"
]
}delete_linkedin_publication 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 publication 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_publication: 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_publication 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_publication 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_publication. 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_publication 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.