run_flow_v2 · Visual Annotation MCP: Risk & Policy

WHAT IT DOES

What run_flow_v2 does on Visual Annotation MCP

AI agents invoke run_flow_v2 to trigger actions in Visual Annotation MCP. 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 IT NEEDS A POLICY

Why run_flow_v2 needs a policy

A flow-running tool on a browser automation server would execute a sequence of actions whose effects depend on the flow definition and parameters provided. This fits the Execute category (triggers external operations whose effects depend on arguments).

From the tool's definition Tool name 'run_flow_v2' suggests execution of a workflow or sequence of operations. The server context shows the tool coexists with interaction methods (click_by_role, click_by_selector, check_uncheck) and assertion tools, indicating it likely orchestrates…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_flow_v2 Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_flow_v2": {
      "limits": [
        {
          "counter": "run_flow_v2_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about run_flow_v2

What does the run_flow_v2 tool do? +

run_flow_v2. It is categorised as a Execute tool in the Visual Annotation MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_flow_v2? +

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

What risk level is run_flow_v2? +

run_flow_v2 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_flow_v2? +

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

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

run_flow_v2 is provided by the Visual Annotation MCP server (mstocker1/visual_annotation_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

run_flow_v2 is one line of Visual Annotation's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →