update_campaign · Posteverywhere MCP: Risk & Policy

WHAT IT DOES

What update_campaign does on Posteverywhere

AI agents use update_campaign to create or update resources in Posteverywhere — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Posteverywhere environment.

WHY IT NEEDS A POLICY

Why update_campaign needs a policy

This tool creates or modifies campaign data reversibly. While it affects social media campaign state, the changes are non-destructive—campaign names, descriptions, colors, and active/archived status can be reverted. The severity is medium rather than high because campaign updates have limited blast radius compared to posting to millions of followers or deleting content.

From the tool's definition Tool description states it "Update[s] a campaign" with modifiable fields: "name, description, color, or active/archived status." The verb "update" and reversible nature of modifying campaign metadata (not deletion or financial transaction) classify this as…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_campaign Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_campaign": {
      "limits": [
        {
          "counter": "update_campaign_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Posteverywhere, so you can run agents against it safely.

FAQ

Questions about update_campaign

What does the update_campaign tool do? +

Update a campaign on PostEverywhere (name, description, color, or active/archived status). It is categorised as a Write tool in the Posteverywhere MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_campaign? +

Register the Posteverywhere MCP server in PolicyLayer and add a rule for update_campaign: 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 Posteverywhere. Nothing to install.

What risk level is update_campaign? +

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

Can I rate-limit update_campaign? +

Yes. Add a rate_limit block to the update_campaign 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 update_campaign completely? +

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

update_campaign is provided by the Posteverywhere MCP server (posteverywhere/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.