Cancel a scheduled post or delete a draft. Cannot delete a post that has already been published — use the platform\
AI agents call cancel_post to permanently remove resources in Viraly MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of draft and scheduled post data. Although the scope is limited to non-published content, deletion is a destructive operation that cannot be undone. The high severity reflects the potential for an AI agent to accidentally remove user-created content (drafts, scheduled posts) without recourse.
From the tool's definition The tool description states 'Cancel a scheduled post or delete a draft', with 'delete' indicating irreversible removal of content.
Attacks that exploit this kind of access
Cancel a scheduled post or delete a draft. Cannot delete a post that has already been published — use the platform\. It is categorised as a Destructive tool in the Viraly MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Viraly MCP Server MCP server in PolicyLayer and add a rule for cancel_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 Viraly MCP Server. Nothing to install.
cancel_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_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_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_post is provided by the Viraly MCP Server MCP server (viraly-io/viraly-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 →