linkedin_delete_post
Delete a LinkedIn post by its URN
This record as markdown: /tools/io-github-alifanov-scopegate/linkedin-delete-post.md
What linkedin_delete_post does on ScopeGate
AI agents call linkedin_delete_post to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why linkedin_delete_post is rated Critical
Deleting a LinkedIn post is an irreversible action that permanently removes user-generated content from a public platform. This cannot be undone and represents loss of data/content. While not as severe as financial damage, the destructive nature and potential reputational impact (e.g., an AI agent deleting important business posts) warrant a 'high' severity rating.
From the tool's definition Tool name is 'linkedin_delete_post' with description 'Delete a LinkedIn post by its URN'. The verb 'delete' and the irreversible nature of removing published content from LinkedIn clearly indicate a destructive operation.
Attacks that exploit this kind of access
The rule that runs linkedin_delete_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linkedin_delete_post, this is the rule to start with:
linkedin_delete_post is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every linkedin_delete_post call is checked against it from then on.
Questions about linkedin_delete_post
Delete a LinkedIn post by its URN. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate 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 ScopeGate. 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 ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue