crow_kb_publish_article
Publish a draft article (makes it visible based on collection visibility). Uses a two-step confirmation: first call returns a preview and token, second call with the token executes.
This record as markdown: /tools/kh0pper-crow/crow-kb-publish-article.md
What crow_kb_publish_article does on Crow
AI agents use crow_kb_publish_article 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_kb_publish_article is rated Medium
Publishing an article modifies data state (draft → published) and affects visibility, making it a Write operation rather than Read. The two-step confirmation pattern with preview + token reduces accidental misuse risk but doesn't change the fundamental nature of the action.
From the tool's definition Tool description states 'Publish a draft article (makes it visible based on collection visibility)' — this creates/modifies the visibility state of content from draft to published, a reversible change.
Attacks that exploit this kind of access
The rule that runs crow_kb_publish_article 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_kb_publish_article, this is the rule to start with:
crow_kb_publish_article 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_kb_publish_article call is checked against it from then on.
Questions about crow_kb_publish_article
Publish a draft article (makes it visible based on collection visibility). Uses a two-step confirmation: first call returns a preview and token, second call with the token executes. 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_kb_publish_article: 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_kb_publish_article 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_kb_publish_article 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_kb_publish_article. 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_kb_publish_article 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