input.click_xy
Click at native screen coordinates (0…native_width-1, 0…native_height-1 from screen.observe). Last resort when no suitable UIA target exists — prefer input.click_target. Never use JPEG/downscaled pixel coords. Side effect: real mouse click on the remote desktop.
This record as markdown: /tools/com-glasswarp-mcp-server/input.click-xy.md
What input.click_xy does on Glasswarp
AI agents invoke input.click_xy to trigger actions in Glasswarp. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
x | integer | Yes | Native X (0…native_width-1) |
y | integer | Yes | Native Y (0…native_height-1) |
button | string | — | Mouse button (default left) |
double | boolean | — | If true, double-click |
session_id | string | Yes | Active session id |
Parameters from the server's own tool schema.
Why input.click_xy is rated High
This tool executes a mouse click on a remote Windows system. While not destructive by itself, a single misplaced click can trigger deletion, financial transactions, or other high-impact actions depending on UI state.
From the tool's definition Tool performs 'real mouse click on the remote desktop' — a direct action with external effects on a Windows PC.
Attacks that exploit this kind of access
The rule that runs input.click_xy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Glasswarp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For input.click_xy, this is the rule to start with:
input.click_xy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Glasswarp, apply this rule, and every input.click_xy call is checked against it from then on.
Questions about input.click_xy
Click at native screen coordinates (0…native_width-1, 0…native_height-1 from screen.observe). Last resort when no suitable UIA target exists — prefer input.click_target. Never use JPEG/downscaled pixel coords. Side effect: real mouse click on the remote desktop. It is categorised as a Execute tool in the Glasswarp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
input.click_xy accepts 5 parameters: x, y, button, double, session_id. Required: x, y, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Glasswarp MCP server in PolicyLayer and add a rule for input.click_xy: 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 Glasswarp. Nothing to install.
input.click_xy 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 input.click_xy 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 input.click_xy. 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.
input.click_xy is provided by the Glasswarp MCP server (https://mcp.glasswarp.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Glasswarp, and thousands of servers like it.
Across the catalogue