highlight_element · Visual Annotation MCP: Risk & Policy

WHAT IT DOES

What highlight_element does on Visual Annotation MCP

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

Based on the server context (browser automation/visual annotation) and sibling tools that perform browser interactions, 'highlight_element' likely draws a visual highlight or annotation on a page element — an Execute-level browser action. Confidence is reduced due to empty description; it could also be purely Read/visual. Most severe plausible interpretation given context is Execute.

From the tool's definition Tool name 'highlight_element' on a server that performs browser actions (click, annotate, screenshot). Description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

highlight_element Rate-limited

highlight_element 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": {
    "highlight_element": {
      "limits": [
        {
          "counter": "highlight_element_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 highlight_element

What does the highlight_element tool do? +

highlight_element. 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 highlight_element? +

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

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

Can I rate-limit highlight_element? +

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

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

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