ui_click_by_id · K-Personal MCP: Risk & Policy

WHAT IT DOES

What ui_click_by_id does on K-Personal MCP

AI agents invoke ui_click_by_id to trigger actions in K-Personal MCP. 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 ui_click_by_id needs a policy

This tool performs a UI interaction (clicking a control) via Windows UI Automation. Clicking UI elements triggers external operations whose effects depend on which control is targeted — it could submit forms, trigger actions, open dialogs, etc. This falls under Execute as it drives UI actions with variable side effects depending on arguments.

From the tool's definition ui_click_by_id — clicks a UI control identified by AutomationId; described as 'AutomationId 로 컨트롤 클릭' (control click by AutomationId)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ui_click_by_id Rate-limited

ui_click_by_id 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": {
    "ui_click_by_id": {
      "limits": [
        {
          "counter": "ui_click_by_id_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 K-Personal MCP, so you can run agents against it safely.

FAQ

Questions about ui_click_by_id

What does the ui_click_by_id tool do? +

AutomationId 로 컨트롤 클릭. ui_click_by_name 보다 안정적. It is categorised as a Execute tool in the K-Personal MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ui_click_by_id? +

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

What risk level is ui_click_by_id? +

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

Can I rate-limit ui_click_by_id? +

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

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

ui_click_by_id is provided by the K-Personal MCP server (lee30934-byte/k-personal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.