wf_create_post
Create a post. If collection is omitted, the post is a draft (anonymous post, not federated until published to a collection). Rate-limited: 10/hour.
This record as markdown: /tools/kh0pper-crow/wf-create-post.md
What wf_create_post does on Crow
AI agents use wf_create_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_create_post is rated Medium
This tool creates new content (posts/drafts) in the project management system. It is a Write operation because it creates or modifies data reversibly. Severity is low because the blast radius of an AI misusing this to create unwanted posts is limited—posts can be edited or deleted, and drafts are not immediately federated. The rate limit (10/hour) further constrains potential abuse.
From the tool's definition Tool name contains 'create' and description states 'Create a post'. The action is reversible (posts can typically be edited or deleted), and creates data without deletion or financial implications.
Attacks that exploit this kind of access
The rule that runs wf_create_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_create_post, this is the rule to start with:
wf_create_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_create_post call is checked against it from then on.
Questions about wf_create_post
Create a post. If collection is omitted, the post is a draft (anonymous post, not federated until published to a collection). 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_create_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_create_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_create_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_create_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_create_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