Cancel a queued cross-post before its scheduled_at fires. Idempotent — cancelling an already-published entry returns the published target_post_id. Cancelling an already-cancelled entry is a no-op.
AI agents call crow_crosspost_cancel to permanently remove resources in Crow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a scheduled cross-post is an irreversible action in the sense that it removes the queued job and cannot be undone once cancelled (the scheduled post will not be sent). While the description notes idempotency and that cancelling an already-published entry simply returns the published ID, the primary action of cancelling a pending/queued operation is not reversible.
From the tool's definition Cancel a queued cross-post before its scheduled_at fires
Documented attack patterns abuse exactly the kind of access crow_crosspost_cancel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_crosspost_cancel:
{
"version": "1",
"default": "deny",
"hide": [
"crow_crosspost_cancel"
]
} crow_crosspost_cancel 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 queued cross-post before its scheduled_at fires. Idempotent — cancelling an already-published entry returns the published target_post_id. Cancelling an already-cancelled entry is a no-op. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_crosspost_cancel: 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 Crow. Nothing to install.
crow_crosspost_cancel 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 crow_crosspost_cancel 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 crow_crosspost_cancel. 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.
crow_crosspost_cancel is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.