dismiss_common_popups · Visual Annotation MCP: Risk & Policy

WHAT IT DOES

What dismiss_common_popups does on Visual Annotation MCP

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

This tool performs browser actions (clicking/dismissing popups, cookie banners, modals) which are external operations that interact with a live browser session. It triggers UI interactions whose effects depend on what popups are present on the page, fitting the Execute category. Severity is medium as misuse could dismiss important modals or consent dialogs unintentionally.

From the tool's definition dismiss_common_popups: 'Best-effort dismiss of cookie/modals using common labels and close icons'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dismiss_common_popups Rate-limited

dismiss_common_popups 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": {
    "dismiss_common_popups": {
      "limits": [
        {
          "counter": "dismiss_common_popups_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 dismiss_common_popups

What does the dismiss_common_popups tool do? +

Best-effort dismiss of cookie/modals using common labels and close icons. 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 dismiss_common_popups? +

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

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

Can I rate-limit dismiss_common_popups? +

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

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

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