Click a UI element in the front window by description or title
AI agents invoke affinity_click_ui to trigger actions in Affinity MCP Server. 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.
This tool triggers UI interactions (clicking) in the Affinity creative suite via AppleScript/System Events. Clicking UI elements can trigger arbitrary application actions depending on which element is clicked — ranging from benign navigation to destructive operations like deleting layers or closing documents without saving.
From the tool's definition Click a UI element in the front window by description or title
Attacks that exploit this kind of access
Click a UI element in the front window by description or title. It is categorised as a Execute tool in the Affinity MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Affinity MCP Server MCP server in PolicyLayer and add a rule for affinity_click_ui: 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 Affinity MCP Server. Nothing to install.
affinity_click_ui 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 affinity_click_ui 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 affinity_click_ui. 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.
affinity_click_ui is provided by the Affinity MCP Server MCP server (sekharmalla/affinity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →