campaign.advance
Advance exactly one validated OBSERVE-to-ROLLBACK controller state.
This record as markdown: /tools/visionmcp/campaign.advance.md
What campaign.advance does on Visionmcp
AI agents invoke campaign.advance to trigger actions in Visionmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why campaign.advance is rated High
The tool executes a state transition in a controller workflow (OBSERVE-to-ROLLBACK), which is an external operation with side effects. It is not purely reading data, nor purely writing/creating a record.
From the tool's definition 'Advance exactly one validated OBSERVE-to-ROLLBACK controller state' — triggers a state machine transition in a controller pipeline
Attacks that exploit this kind of access
The rule that runs campaign.advance 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.advance, this is the rule to start with:
campaign.advance stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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.advance call is checked against it from then on.
Questions about campaign.advance
Advance exactly one validated OBSERVE-to-ROLLBACK controller state. It is categorised as a Execute tool in the Visionmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vision MCP server in PolicyLayer and add a rule for campaign.advance: 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.advance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the campaign.advance 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.advance. 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.advance 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.
Across the catalogue