Delete a LinkedIn post.
AI agents call delete_linkedin_post 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 LinkedIn posts, which cannot be undone. The action destroys user-generated content. While the impact is limited to individual posts (not system-wide), the irreversible nature and potential for abuse (deleting important professional communications, announcements, or records) warrants high severity. Classified as Destructive rather than Write because deletion cannot be reversed.
From the tool's definition Tool name explicitly states 'delete_linkedin_post' and description confirms 'Delete a LinkedIn post.' Deletion is irreversible data destruction.
Attacks that exploit this kind of access
Delete a LinkedIn post. 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_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 MCP Server. Nothing to install.
delete_linkedin_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 delete_linkedin_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 delete_linkedin_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.
delete_linkedin_post is provided by the LinkedIn MCP Server MCP server (selvin-paul-raj/linkedin-mcp-server). 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 →