Critical Risk →

cancel_post

Cancel a scheduled post (refunds your post quota)

Part of the Postbolt server.

cancel_post can permanently delete data in Postbolt, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE POSTBOLT →

Free to start. No card required.

AI agents may call cancel_post to permanently remove or destroy resources in Postbolt. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call cancel_post in a loop, permanently destroying resources in Postbolt. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_post"
  ]
}

See the full Postbolt policy for all 7 tools.

Get this rule live on your own Postbolt server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY POSTBOLT →

These attack patterns abuse exactly the kind of access cancel_post gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cancel_post only ever does what you allow.

SECURE POSTBOLT →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the cancel_post tool do? +

Cancel a scheduled post (refunds your post quota). It is categorised as a Destructive tool in the Postbolt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cancel_post? +

Register the Postbolt 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 Postbolt. Nothing to install.

What risk level is cancel_post? +

cancel_post is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_post? +

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.

How do I block cancel_post completely? +

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.

What MCP server provides cancel_post? +

cancel_post is provided by the Postbolt MCP server (postbolt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Postbolt tool call.

Deterministic rules across all 7 Postbolt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.