Share a blog post with a Crow peer via P2P
AI agents use crow_share_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.
This tool creates and distributes shared data (a blog post) across the P2P network, which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely retrieve information (not Read). The medium severity reflects that misuse could spam peers or share inappropriate content, but the effects are reversible and limited in scope.
From the tool's definition The tool "Share a blog post with a Crow peer via P2P" performs a write action by creating/sending a shared resource to another peer. The description indicates it modifies the state of shared content across the P2P network.
Documented attack patterns abuse exactly the kind of access crow_share_post 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_share_post:
{
"version": "1",
"default": "deny",
"tools": {
"crow_share_post": {
"limits": [
{
"counter": "crow_share_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}crow_share_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.
Free to start. No card required.
Share a blog post with a Crow peer via P2P. 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_share_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_share_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_share_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_share_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_share_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.
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.