check_uncheck · Visual Annotation MCP: Risk & Policy

WHAT IT DOES

What check_uncheck does on Visual Annotation MCP

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

This tool performs a browser interaction (checking/unchecking a form element), which is an active operation that triggers UI state changes and potentially form submissions or other side effects depending on the page context. It falls under Execute as it triggers external browser actions whose effects depend on arguments.

From the tool's definition Check or uncheck a checkbox/radio using selector or element id

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

check_uncheck Rate-limited

check_uncheck 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": {
    "check_uncheck": {
      "limits": [
        {
          "counter": "check_uncheck_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 check_uncheck

What does the check_uncheck tool do? +

Check or uncheck a checkbox/radio using selector or element id. 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 check_uncheck? +

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

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

Can I rate-limit check_uncheck? +

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

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

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