drag_element · MacWright MCP: Risk & Policy

WHAT IT DOES

What drag_element does on MacWright

AI agents invoke drag_element to trigger actions in MacWright. 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 drag_element needs a policy

This tool triggers browser automation actions (drag-and-drop) in Safari, executing UI interactions that can manipulate web page state. It's an Execute-category tool as it performs external browser operations whose effects depend on the arguments (source/target CSS selectors). The blast radius is medium since it can manipulate web content but is limited to drag-and-drop interactions within Safari.

From the tool's definition Drag one DOM element to another in Safari — drag-and-drop automation using CSS selectors... performs the drag. Auto-detects drag method: HTML5 DragEvent API

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drag_element Rate-limited

drag_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": {
    "drag_element": {
      "limits": [
        {
          "counter": "drag_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 MacWright, so you can run agents against it safely.

FAQ

Questions about drag_element

What does the drag_element tool do? +

Drag one DOM element to another in Safari — drag-and-drop automation using CSS selectors. Scrolls both elements into view, computes their screen coordinates, then performs the drag. Auto-detects drag method: HTML5 DragEvent API for draggable=. It is categorised as a Execute tool in the MacWright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on drag_element? +

Register the MacWright MCP server in PolicyLayer and add a rule for drag_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 MacWright. Nothing to install.

What risk level is drag_element? +

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

Can I rate-limit drag_element? +

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

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

drag_element is provided by the MacWright MCP server (ruchit-p/macwright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.