Delete a LinkedIn post by its URN (e.g., 'urn:li:share:123').
AI agents call linkedin_delete_post to permanently remove resources in LinkedIn Custom 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 data (a LinkedIn post) from the user's account. Deletion operations are irreversible and represent the most severe category of risk. An AI agent given uncontrolled access could delete important professional content, posts with business value, or posts with engagement/audience, causing reputational or business harm.
From the tool's definition Tool name contains 'delete' and description states 'Delete a LinkedIn post by its URN'. Deletion of posts is irreversible and cannot be undone.
Documented attack patterns abuse exactly the kind of access linkedin_delete_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Custom MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for linkedin_delete_post:
{
"version": "1",
"default": "deny",
"hide": [
"linkedin_delete_post"
]
}linkedin_delete_post 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 LinkedIn post by its URN (e.g., 'urn:li:share:123'). It is categorised as a Destructive tool in the LinkedIn Custom MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LinkedIn Custom MCP Server MCP server in PolicyLayer and add a rule for linkedin_delete_post: 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 Custom MCP Server. Nothing to install.
linkedin_delete_post 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 linkedin_delete_post 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_delete_post. 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_delete_post is provided by the LinkedIn Custom MCP Server MCP server (saramali15792/linkedin_mcp_custom_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn Custom 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.
17 LinkedIn Custom MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.