wait_for_selector · Visual Annotation MCP: Risk & Policy

WHAT IT DOES

What wait_for_selector does on Visual Annotation MCP

AI agents invoke wait_for_selector 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 wait_for_selector needs a policy

This tool executes a wait/polling operation that monitors DOM state and can block execution flow until a condition is met. While non-destructive, it is an active operation that affects browser behavior and interacts with external systems (web pages). It falls under Execute rather than Read because it modifies the interaction flow of a browser session, not merely observing data.

From the tool's definition Tool description states it waits for a selector to reach a state change, implying active monitoring and blocking operations that control page interaction flow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_selector Rate-limited

wait_for_selector 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": {
    "wait_for_selector": {
      "limits": [
        {
          "counter": "wait_for_selector_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 wait_for_selector

What does the wait_for_selector tool do? +

Wait for a selector to reach attached/detached/visible/hidden state. 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 wait_for_selector? +

Register the Visual Annotation MCP server in PolicyLayer and add a rule for wait_for_selector: 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 wait_for_selector? +

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

Can I rate-limit wait_for_selector? +

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

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

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