Mark a queued cross-post as published (called by the target bundle
AI agents use crow_crosspost_mark_published 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.
This tool modifies the status of a cross-post from queued to published, which is a reversible write operation. It does not delete data (Destructive), does not move money (Financial), does not execute arbitrary code (Execute), and does not merely read (Read).
From the tool's definition Tool name includes 'mark_published' and description states it marks 'a queued cross-post as published', indicating a state change operation on existing data.
Documented attack patterns abuse exactly the kind of access crow_crosspost_mark_published 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_crosspost_mark_published:
{
"version": "1",
"default": "deny",
"tools": {
"crow_crosspost_mark_published": {
"limits": [
{
"counter": "crow_crosspost_mark_published_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}crow_crosspost_mark_published 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.
Mark a queued cross-post as published (called by the target bundle. 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_crosspost_mark_published: 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_crosspost_mark_published 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_crosspost_mark_published 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_crosspost_mark_published. 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_crosspost_mark_published 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.