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.
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.
Publishing an article modifies the visibility and status of content in the knowledge base from draft (unpublished) to published. This is a reversible Write operation—the article can typically be unpublished or reverted. It is not Destructive since publishing is not irreversible (articles can be unpublished).
From the tool's definition Tool name contains 'publish' and description states it 'makes it visible' and 'executes' an action that transitions content from draft to published state. The two-step confirmation pattern confirms this is a content modification operation.
Documented attack patterns abuse exactly the kind of access crow_kb_publish_article gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_kb_publish_article:
{
"version": "1",
"default": "deny",
"tools": {
"crow_kb_publish_article": {
"limits": [
{
"counter": "crow_kb_publish_article_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.