High Risk →

desktop_drag

Drag from (from_x, from_y) to (to_x, to_y) on the sandbox desktop.

How to control desktop_drag ↓

What desktop_drag does on Taw Computer

AI agents invoke desktop_drag to trigger actions in Taw Computer. 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.

High Risk

Why desktop_drag needs a policy

This tool performs a GUI drag action on a desktop environment, which is an interactive operation that triggers external effects depending on arguments (e.g., moving files, rearranging UI elements). It fits the Execute category as it drives actions in a live desktop environment.

From the tool's definition Drag from (from_x, from_y) to (to_x, to_y) on the sandbox desktop

Documented attack patterns abuse exactly the kind of access desktop_drag gives an agent:

How to control desktop_drag

PolicyLayer is an MCP gateway — it sits between your AI agents and Taw Computer, and nothing reaches the server without passing your rules. This is the rule we recommend for desktop_drag:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "desktop_drag": {
      "limits": [
        {
          "counter": "desktop_drag_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Taw Computer — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about desktop_drag

What does the desktop_drag tool do? +

Drag from (from_x, from_y) to (to_x, to_y) on the sandbox desktop. It is categorised as a Execute tool in the Taw Computer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on desktop_drag? +

Register the Taw Computer MCP server in PolicyLayer and add a rule for desktop_drag: 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 Taw Computer. Nothing to install.

What risk level is desktop_drag? +

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

Can I rate-limit desktop_drag? +

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

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

desktop_drag is provided by the Taw Computer MCP server (tawgroup/taw-computer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Taw Computer tool call.

Start from Taw Computer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

36 Taw Computer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.