bytebot_click · ByteBot MCP Server MCP: Risk & Policy

WHAT IT DOES

What bytebot_click does on ByteBot MCP Server

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

This tool executes direct desktop mouse click actions at arbitrary screen coordinates. An AI agent could misuse this to interact with any UI element — including buttons that trigger destructive, financial, or other high-impact operations — making it an Execute-category tool with high severity due to its broad blast radius in a desktop automation context.

From the tool's definition Click at specific screen coordinates. Supports left, right, and middle mouse buttons, as well as double-clicks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bytebot_click Rate-limited

bytebot_click 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_click": {
      "limits": [
        {
          "counter": "bytebot_click_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_click

What does the bytebot_click tool do? +

Click at specific screen coordinates. Supports left, right, and middle mouse buttons, as well as double-clicks. 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_click? +

Register the ByteBot MCP Server MCP server in PolicyLayer and add a rule for bytebot_click: 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_click? +

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

Can I rate-limit bytebot_click? +

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

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

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