Medium Risk

crow_campaign_update_post

Update a post

How to control crow_campaign_update_post ↓

What crow_campaign_update_post does on Crow

AI agents use crow_campaign_update_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.

Medium Risk

Why crow_campaign_update_post needs a policy

This tool creates or modifies data reversibly by updating a post within the project management system. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial).

From the tool's definition Tool name includes 'update' and description states 'Update a post', indicating modification of existing data.

Documented attack patterns abuse exactly the kind of access crow_campaign_update_post gives an agent:

How to control crow_campaign_update_post

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_campaign_update_post:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_campaign_update_post": {
      "limits": [
        {
          "counter": "crow_campaign_update_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

crow_campaign_update_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.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_campaign_update_post

What does the crow_campaign_update_post tool do? +

Update a post. 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.

How do I enforce a policy on crow_campaign_update_post? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_campaign_update_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.

What risk level is crow_campaign_update_post? +

crow_campaign_update_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit crow_campaign_update_post? +

Yes. Add a rate_limit block to the crow_campaign_update_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.

How do I block crow_campaign_update_post completely? +

Set action: deny in the PolicyLayer policy for crow_campaign_update_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.

What MCP server provides crow_campaign_update_post? +

crow_campaign_update_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.

Enforce policy on every Crow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.