crow_campaign_approve_posts
Batch approve posts by ID. Moves them from pending_approval/draft to approved.
This record as markdown: /tools/kh0pper-crow/crow-campaign-approve-posts.md
What crow_campaign_approve_posts does on Crow
AI agents use crow_campaign_approve_posts 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_campaign_approve_posts is rated Medium
The tool creates or modifies data reversibly by changing post approval status. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial).
From the tool's definition Tool description states it 'Batch approve posts by ID. Moves them from pending_approval/draft to approved.' This is a state-modifying operation that changes post status from pending/draft to approved.
Attacks that exploit this kind of access
The rule that runs crow_campaign_approve_posts 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_campaign_approve_posts, this is the rule to start with:
crow_campaign_approve_posts 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_campaign_approve_posts call is checked against it from then on.
Questions about crow_campaign_approve_posts
Batch approve posts by ID. Moves them from pending_approval/draft to approved. 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_campaign_approve_posts: 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_campaign_approve_posts 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_campaign_approve_posts 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_campaign_approve_posts. 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_campaign_approve_posts 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