Cancel a scheduled post.
AI agents call cancel_scheduled_post to permanently remove resources in LinkedIn Intelligence MCP Server — 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 entry is gone and would need to be recreated from scratch. This places it in the Destructive category. Severity is medium because the blast radius is limited to losing a single piece of scheduled content, but it could cause reputational or business impact if important posts are accidentally cancelled.
From the tool's definition 'Cancel a scheduled post' — cancelling a scheduled post irreversibly removes it from the publishing queue and cannot be undone
Documented attack patterns abuse exactly the kind of access cancel_scheduled_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_scheduled_post:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_scheduled_post"
]
}cancel_scheduled_post disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel a scheduled post. It is categorised as a Destructive tool in the LinkedIn Intelligence MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for cancel_scheduled_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 Intelligence MCP Server. Nothing to install.
cancel_scheduled_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 cancel_scheduled_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 cancel_scheduled_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.
cancel_scheduled_post is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.