iac_mcp_click_element

Click a UI element identified by a reference from ui_snapshot. Usage: 1. First call ui_snapshot to get element references 2. Find the element you want to click 3. Pass its reference ID to this tool Example workflow: 1. ui_snapshot(

Server Iac jsavin/iac-mcp
Category Execute
Risk class High
Parameters 00 required

What iac_mcp_click_element does on Iac

AI agents invoke iac_mcp_click_element to trigger actions in Iac. 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 iac_mcp_click_element needs a policy

This tool performs UI automation by clicking elements in native macOS applications (Finder, Mail, Safari, etc.). Clicking UI elements can trigger arbitrary application actions — submitting forms, confirming dialogs, deleting files, sending emails, or executing any button/menu action.

From the tool's definition Click a UI element identified by a reference from ui_snapshot

Questions about iac_mcp_click_element

What does the iac_mcp_click_element tool do? +

Click a UI element identified by a reference from ui_snapshot. Usage: 1. First call ui_snapshot to get element references 2. Find the element you want to click 3. Pass its reference ID to this tool Example workflow: 1. ui_snapshot(. It is categorised as a Execute tool in the Iac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on iac_mcp_click_element? +

Register the Iac MCP server in PolicyLayer and add a rule for iac_mcp_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 Iac. Nothing to install.

What risk level is iac_mcp_click_element? +

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

Can I rate-limit iac_mcp_click_element? +

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

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

iac_mcp_click_element is provided by the Iac MCP server (jsavin/iac-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.