High Risk →

click_image_if_found

Find and click an image on the screen

How to control click_image_if_found ↓

AI agents invoke click_image_if_found 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.

High Risk

This tool performs a screen-based GUI automation action by locating an image and clicking it. Clicking UI elements can trigger arbitrary application behavior (buttons, links, dialogs, confirmations), making it an Execute-category tool. The blast radius is high because a misused click could confirm destructive dialogs, submit forms, or trigger unintended system operations.

From the tool's definition 'Find and click an image on the screen' — triggers a UI interaction (mouse click) on the Windows system based on visual matching

Documented attack patterns abuse exactly the kind of access click_image_if_found gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for click_image_if_found:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "click_image_if_found": {
      "limits": [
        {
          "counter": "click_image_if_found_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

click_image_if_found 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.

  1. Create a free account and register Mcp Windows — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the click_image_if_found tool do? +

Find and click an image on the screen. 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_image_if_found? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for click_image_if_found: 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_image_if_found? +

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

Can I rate-limit click_image_if_found? +

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

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

click_image_if_found 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.

Enforce policy on every Mcp Windows tool call.

Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.