click_in_window
Click at coordinates relative to a matching window's top-left corner.
This record as markdown: /tools/mcp-control-plane/click-in-window.md
What click_in_window does on Mcp Control Plane
AI agents invoke click_in_window to trigger actions in Mcp Control Plane. 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 click_in_window is rated High
This tool performs UI automation by simulating mouse clicks within application windows. It triggers real interactions with arbitrary application UI, which can cause unpredictable side effects depending on what is clicked — including submitting forms, deleting data, or executing commands. This is an Execute-category action with high severity due to the broad blast radius of uncontrolled click automation.
From the tool's definition Click at coordinates relative to a matching window's top-left corner.
Attacks that exploit this kind of access
The rule that runs click_in_window safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For click_in_window, this is the rule to start with:
click_in_window 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 Mcp Control Plane, apply this rule, and every click_in_window call is checked against it from then on.
Questions about click_in_window
Click at coordinates relative to a matching window's top-left corner. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for click_in_window: 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 Mcp Control Plane. Nothing to install.
click_in_window 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 click_in_window 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 click_in_window. 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.
click_in_window is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue