click_at_coordinates

Click at specific screen coordinates

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mukul975-mcp-windows-automation/click-at-coordinates.md

WHAT IT DOES

What click_at_coordinates does on Mcp Windows

AI agents invoke click_at_coordinates to trigger actions in Mcp Windows. 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.

RISK

Why click_at_coordinates is rated High

Clicking at arbitrary screen coordinates can trigger any UI element, button, link, or control visible on screen. In the context of a Windows automation server with 200+ tools, this could activate destructive operations, confirm dialogs, submit forms, or interact with any application.

From the tool's definition 'Click at specific screen coordinates' — triggers a UI interaction at arbitrary screen positions on a Windows system

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs click_at_coordinates safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For click_at_coordinates, this is the rule to start with:

click_at_coordinates Rate-limited

click_at_coordinates 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": {
    "click_at_coordinates": {
      "limits": [
        {
          "counter": "click_at_coordinates_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every click_at_coordinates call is checked against it from then on.

FAQ

Questions about click_at_coordinates

What does the click_at_coordinates tool do? +

Click at specific screen coordinates. It is categorised as a Execute tool in the Mcp Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on click_at_coordinates? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for click_at_coordinates: 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 Windows. Nothing to install.

What risk level is click_at_coordinates? +

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

Can I rate-limit click_at_coordinates? +

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

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

click_at_coordinates is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Windows, and thousands of servers like it.

This server

All 441 Mcp Windows tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →