Permanently delete a LinkedIn post.
AI agents call linkedin_delete_post to permanently remove resources in AmplifyrMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a LinkedIn post) and cannot be undone. Deletion operations that cannot be reversed fall under the Destructive category. The severity is high because an AI agent misusing this tool could permanently remove important published content, damaging reputation or losing valuable engagement history.
From the tool's definition Tool name is 'linkedin_delete_post' with description 'Permanently delete a LinkedIn post.' The use of 'Permanently delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Permanently delete a LinkedIn post. It is categorised as a Destructive tool in the AmplifyrMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amplifyr 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 AmplifyrMCP. 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 Amplifyr MCP server (supersaiyane/amplifyrmcp). 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 →