This record as markdown: /tools/kh0pper-crow/crow-campaign-update.md
What crow_campaign_update does on Crow
AI agents use crow_campaign_update 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_update is rated Medium
This tool creates or modifies campaign data reversibly. 'Update' is a classic Write operation—changes can be undone, data is not permanently deleted, and no code execution or financial transactions are implied. Severity is medium because unauthorized campaign updates in a project management system could disrupt workflows, but the blast radius is limited to campaign data rather than system-wide or financial impact.
From the tool's definition Tool name contains 'update' which modifies existing data (a campaign). Description states 'Update a campaign' indicating reversible data modification.
Attacks that exploit this kind of access
The rule that runs crow_campaign_update 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_update, this is the rule to start with:
crow_campaign_update 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_update call is checked against it from then on.
Questions about crow_campaign_update
Update a campaign. 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_update: 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_update 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_update 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_update. 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_update 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