Clicks at a position in the webview. Provide x/y coordinates directly, or provide a selector (ref from query_page map mode, or id/class/tag/text) to auto-resolve coordinates. For selector-based clicks, this first finds the element then clicks its center. IMPORTANT: Do not guess x/y coordinates fr...
AI agents invoke click to trigger actions in Tauri Plugin. 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.
Simulating clicks in a Tauri application UI can trigger arbitrary application actions — form submissions, navigation, deletions, purchases — depending on what the UI element does. This is an Execute-category tool because it triggers external operations whose effects depend on the arguments. Severity is high because an AI agent could misuse this to click destructive or financial UI elements within the application.
From the tool's definition Clicks at a position in the webview... triggers external operations via input simulation; can resolve selectors and click UI elements programmatically
Documented attack patterns abuse exactly the kind of access click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tauri Plugin, and nothing reaches the server without passing your rules. This is the rule we recommend for click:
{
"version": "1",
"default": "deny",
"tools": {
"click": {
"limits": [
{
"counter": "click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}click 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.
Free to start. No card required.
Clicks at a position in the webview. Provide x/y coordinates directly, or provide a selector (ref from query_page map mode, or id/class/tag/text) to auto-resolve coordinates. For selector-based clicks, this first finds the element then clicks its center. IMPORTANT: Do not guess x/y coordinates from screenshots — screenshot resolution differs from page CSS coordinates. Preferred workflow: (1) use query_page with mode=. It is categorised as a Execute tool in the Tauri Plugin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tauri Plugin MCP server in PolicyLayer and add a rule for click: 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 Tauri Plugin. Nothing to install.
click 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 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. 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 is provided by the Tauri Plugin MCP server (p3gleg/tauri-plugin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Tauri Plugin tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Tauri Plugin tools catalogued and risk-classified — across an index of 42,500+ MCP servers.