opus_cancel_scheduled_post
Cancel a scheduled social post BEFORE its publishAt time.
This record as markdown: /tools/freshdesk/opus-cancel-scheduled-post.md
What opus_cancel_scheduled_post does on Freshdesk
AI agents call opus_cancel_scheduled_post to permanently remove resources in Freshdesk, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why opus_cancel_scheduled_post is rated Critical
Cancelling a scheduled post is an irreversible action — once cancelled, the scheduled post is gone and the scheduled publication will not occur. This cannot be undone without recreating the post. The blast radius is medium since it affects social media content scheduling but does not delete existing published content or financial data.
From the tool's definition Cancel a scheduled social post BEFORE its publishAt time
Attacks that exploit this kind of access
The rule that runs opus_cancel_scheduled_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For opus_cancel_scheduled_post, this is the rule to start with:
opus_cancel_scheduled_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 Freshdesk, apply this rule, and every opus_cancel_scheduled_post call is checked against it from then on.
Questions about opus_cancel_scheduled_post
Cancel a scheduled social post BEFORE its publishAt time. It is categorised as a Destructive tool in the Freshdesk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshdesk MCP server in PolicyLayer and add a rule for opus_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 Freshdesk. Nothing to install.
opus_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 opus_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 opus_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.
opus_cancel_scheduled_post is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
Across the catalogue