Move the pointer to (x, y) without clicking.
AI agents invoke move to trigger actions in ComputerMate. 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.
Moving the mouse pointer is an external operation that affects the state of the computer's UI without reading or writing data. While it has no direct side effects on its own, it is part of a computer control toolset and constitutes execution of an action on the host environment. Severity is low since moving the pointer alone causes no destructive or meaningful side effect without a subsequent click or interaction.
From the tool's definition Move the pointer to (x, y) without clicking — triggers an external operation (mouse pointer movement) on the controlled computer
Attacks that exploit this kind of access
Move the pointer to (x, y) without clicking. It is categorised as a Execute tool in the ComputerMate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ComputerMate MCP server in PolicyLayer and add a rule for move: 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 ComputerMate. Nothing to install.
move is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the move 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 move. 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.
move is provided by the ComputerMate MCP server (one710/computermate). 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 →