click_element · MCP Tauri Automation MCP: Risk & Policy

WHAT IT DOES

What click_element does on MCP Tauri Automation

AI agents invoke click_element to trigger actions in MCP Tauri Automation. 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 IT NEEDS A POLICY

Why click_element needs a policy

Clicking a UI element triggers external operations within a desktop application whose effects depend on which element is clicked. This is a browser/UI action that executes application logic — it could submit forms, trigger navigation, delete data within the app, or invoke any application-defined behavior. The effect is context-dependent, making it Execute (not merely Read or Write).

From the tool's definition Click a UI element identified by a CSS selector

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_element Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Tauri Automation, so you can run agents against it safely.

FAQ

Questions about click_element

What does the click_element tool do? +

Click a UI element identified by a CSS selector. It is categorised as a Execute tool in the MCP Tauri Automation 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_element? +

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

What risk level is click_element? +

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

Can I rate-limit click_element? +

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

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

click_element is provided by the MCP Tauri Automation MCP server (radek44/mcp-tauri-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.