Cancel a pending scheduled post by ID. Use linkedin_list_scheduled to find IDs.
AI agents call linkedin_cancel_scheduled 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.
Cancelling a scheduled post is an irreversible action — once cancelled, the scheduled post is removed and the planned publication is permanently abandoned. This cannot be undone, making it Destructive rather than Write. Misuse by an AI agent could silently remove scheduled content without user awareness.
From the tool's definition Cancel a pending scheduled post by ID
Attacks that exploit this kind of access
Cancel a pending scheduled post by ID. Use linkedin_list_scheduled to find IDs. 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_cancel_scheduled: 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_cancel_scheduled 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_cancel_scheduled 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_cancel_scheduled. 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_cancel_scheduled 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 →