Get the current mouse cursor position. Returns {x, y} coordinates.
AI agents call bytebot_cursor_position to retrieve information from ByteBot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool simply reads and returns the current cursor position as data. It has no side effects, does not execute code or commands, does not modify state, and does not delete or move data. This is a straightforward read/query operation with minimal security risk even if misused by an agent—knowing cursor position alone cannot cause harm.
From the tool's definition Tool name and description: 'Get the current mouse cursor position. Returns {x, y} coordinates.' This is a query operation that retrieves state information without modifying or executing anything.
Attacks that exploit this kind of access
Get the current mouse cursor position. Returns {x, y} coordinates. It is categorised as a Read tool in the ByteBot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ByteBot MCP Server MCP server in PolicyLayer and add a rule for bytebot_cursor_position: 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.
bytebot_cursor_position is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bytebot_cursor_position 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.
Set action: deny in the PolicyLayer policy for bytebot_cursor_position. 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.
bytebot_cursor_position 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →