Delete a comment from a LinkedIn post
AI agents call linkedin_delete_comment to permanently remove resources in Publora MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a comment cannot be undone and permanently removes data. This is a destructive operation with moderate blast radius if triggered without user intent (e.g., deleting comments from an important professional post). While not as severe as account-level destructive actions, it irreversibly modifies/removes content on a public platform.
From the tool's definition Tool name contains 'delete' and description states 'Delete a comment from a LinkedIn post' — this is an irreversible removal of user-generated content.
Attacks that exploit this kind of access
Delete a comment from a LinkedIn post. It is categorised as a Destructive tool in the Publora MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Publora MCP Server MCP server in PolicyLayer and add a rule for linkedin_delete_comment: 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 Publora MCP Server. Nothing to install.
linkedin_delete_comment 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_comment 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_comment. 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_comment is provided by the Publora MCP Server MCP server (publora/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 →