campaign.pause
Pause a campaign while preserving its exact state and evidence.
This record as markdown: /tools/visionmcp/campaign.pause.md
What campaign.pause does on Visionmcp
AI agents use campaign.pause to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why campaign.pause is rated Medium
Pausing a campaign is a reversible state change — the campaign is stopped temporarily but its state is preserved (not deleted or destroyed). This is a Write operation (modifying the campaign's running state). The blast radius is medium since pausing a campaign could disrupt ongoing operations but is recoverable.
From the tool's definition Pause a campaign while preserving its exact state and evidence
Attacks that exploit this kind of access
The rule that runs campaign.pause safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For campaign.pause, this is the rule to start with:
campaign.pause 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 Visionmcp, apply this rule, and every campaign.pause call is checked against it from then on.
Questions about campaign.pause
Pause a campaign while preserving its exact state and evidence. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for campaign.pause: 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 Visionmcp. Nothing to install.
campaign.pause 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 campaign.pause 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 campaign.pause. 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.
campaign.pause is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue