wf_delete_post
Permanently delete a post. Destructive — the post is gone from the local instance; federated copies on remote servers may persist.
This record as markdown: /tools/kh0pper-crow/wf-delete-post.md
What wf_delete_post does on Crow
AI agents call wf_delete_post 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.
Why wf_delete_post is rated Critical
This tool irreversibly removes data (a post) from the system. The description explicitly categorizes it as 'Destructive' and confirms the action cannot be undone locally. While federated copies may persist on remote servers, the primary instance loses the post permanently.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Permanently delete a post' and 'Destructive' — the post is gone from the local instance; federated copies on remote servers may persist.
Attacks that exploit this kind of access
The rule that runs wf_delete_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wf_delete_post, this is the rule to start with:
wf_delete_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 Crow, apply this rule, and every wf_delete_post call is checked against it from then on.
Questions about wf_delete_post
Permanently delete a post. Destructive — the post is gone from the local instance; federated copies on remote servers may persist. 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 wf_delete_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 Crow. Nothing to install.
wf_delete_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 wf_delete_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 wf_delete_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.
wf_delete_post 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.
More on Crow, and thousands of servers like it.
Across the catalogue