crow_publish_post
Publish a blog post (sets status to published and records timestamp). Returns a preview and confirmation token on first call; pass the token back to execute.
This record as markdown: /tools/kh0pper-crow/crow-publish-post.md
What crow_publish_post does on Crow
AI agents use crow_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 crow_publish_post is rated Medium
Publishing a blog post creates a public, discoverable change to project data that affects visibility and accessibility. While reversible (post can be unpublished), the action is substantive and irreversible in terms of public exposure timeline. Categorized as Write rather than Execute because the tool's purpose is data modification (status + timestamp), not arbitrary code/command execution.
From the tool's definition Tool description states it 'Publish a blog post (sets status to published and records timestamp)', which modifies data by changing post status and recording metadata. The two-step confirmation pattern (preview + token) indicates intentional state change.
Attacks that exploit this kind of access
The rule that runs crow_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 crow_publish_post, this is the rule to start with:
crow_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 crow_publish_post call is checked against it from then on.
Questions about crow_publish_post
Publish a blog post (sets status to published and records timestamp). Returns a preview and confirmation token on first call; pass the token back to execute. 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 crow_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.
crow_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 crow_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 crow_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.
crow_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