wf_publish_post
Move a draft post into a collection (blog), making it public and federated over ActivityPub. Rate-limited: 10/hour.
This record as markdown: /tools/kh0pper-crow/wf-publish-post.md
What wf_publish_post does on Crow
AI agents use wf_publish_post to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why wf_publish_post is rated Medium
Publishing a post is a reversible write operation—the post can be unpublished, deleted, or edited afterward. It does not permanently destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).
From the tool's definition Tool description states it will 'Move a draft post into a collection (blog), making it public and federated over ActivityPub.' This creates and publishes content to a public platform, modifying the state of data by transitioning it from draft to published.
Attacks that exploit this kind of access
The rule that runs wf_publish_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_publish_post, this is the rule to start with:
wf_publish_post stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every wf_publish_post call is checked against it from then on.
Questions about wf_publish_post
Move a draft post into a collection (blog), making it public and federated over ActivityPub. Rate-limited: 10/hour. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for wf_publish_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_publish_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wf_publish_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_publish_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_publish_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.
This server
Across the catalogue