ui_invoke · K-Personal MCP: Risk & Policy

WHAT IT DOES

What ui_invoke does on K-Personal MCP

AI agents invoke ui_invoke 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_invoke needs a policy

This tool triggers execution of arbitrary UI actions. While the name alone might seem neutral, the function—invoking menu items and toolbar buttons—executes whatever operation those UI elements are configured to perform. The actual effect is context-dependent and potentially dangerous (e.g., invoking a 'Delete' menu item, 'Save', 'Send Email', etc.).

From the tool's definition Tool invokes UI patterns (menu items, toolbar buttons, etc.) which triggers external operations. The description explicitly states it 'invokes' UI elements, which constitutes executing actions whose effects depend on what UI element is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ui_invoke Rate-limited

ui_invoke 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_invoke": {
      "limits": [
        {
          "counter": "ui_invoke_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_invoke

What does the ui_invoke tool do? +

InvokePattern (메뉴 항목, 툴바 버튼 등)을 호출합니다. 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_invoke? +

Register the K-Personal MCP server in PolicyLayer and add a rule for ui_invoke: 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_invoke? +

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

Can I rate-limit ui_invoke? +

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

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

ui_invoke 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.