bytebot_move_mouse · ByteBot MCP Server MCP: Risk & Policy

WHAT IT DOES

What bytebot_move_mouse does on ByteBot MCP Server

AI agents invoke bytebot_move_mouse to trigger actions in ByteBot MCP Server. 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 bytebot_move_mouse needs a policy

This tool performs a direct desktop control action (moving the mouse cursor) that constitutes an external operation on the host system. While moving the mouse alone has limited blast radius, it is part of a broader desktop automation chain and constitutes execution of a system-level action rather than a simple read or write of data.

From the tool's definition Move the mouse cursor to specific screen coordinates. Use this to position the cursor before clicking or dragging.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bytebot_move_mouse Rate-limited

bytebot_move_mouse 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": {
    "bytebot_move_mouse": {
      "limits": [
        {
          "counter": "bytebot_move_mouse_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 ByteBot MCP Server, so you can run agents against it safely.

FAQ

Questions about bytebot_move_mouse

What does the bytebot_move_mouse tool do? +

Move the mouse cursor to specific screen coordinates. Use this to position the cursor before clicking or dragging. It is categorised as a Execute tool in the ByteBot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bytebot_move_mouse? +

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

What risk level is bytebot_move_mouse? +

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

Can I rate-limit bytebot_move_mouse? +

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

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

bytebot_move_mouse is provided by the ByteBot MCP Server MCP server (sensuslab/spark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.