ui_menu_bar_click
Clicks a status-bar (menu bar extra / NSStatusItem) item and optionally follows a nested menu path. Best-effort via the app's AX extras menu bar; apps that render fully custom (non-AX) menus may not be reachable (fall back to ui_click at known coords). Requires Accessibility permission.
This record as markdown: /tools/com-local-mcp-local-mcp/ui-menu-bar-click.md
What ui_menu_bar_click does on Local
AI agents invoke ui_menu_bar_click to trigger actions in Local. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | array | — | Nested menu path, e.g. ["App","Settings…"]. |
label | string | — | Status item / menu item title. |
app_bundle_id | string | — | Owner of the status item. |
Parameters from the server's own tool schema.
Why ui_menu_bar_click is rated High
This tool performs UI automation by clicking menu bar items and navigating nested menus via macOS Accessibility APIs. Clicking menu items can trigger arbitrary application actions — launching processes, modifying settings, deleting files, sending emails, etc. — making this an Execute-class tool with high severity since an AI agent could trigger destructive or sensitive operations through menu interactions.
From the tool's definition Clicks a status-bar (menu bar extra / NSStatusItem) item and optionally follows a nested menu path... Requires Accessibility permission.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs ui_menu_bar_click safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_menu_bar_click, this is the rule to start with:
ui_menu_bar_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every ui_menu_bar_click call is checked against it from then on.
Questions about ui_menu_bar_click
Clicks a status-bar (menu bar extra / NSStatusItem) item and optionally follows a nested menu path. Best-effort via the app's AX extras menu bar; apps that render fully custom (non-AX) menus may not be reachable (fall back to ui_click at known coords). Requires Accessibility permission. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
ui_menu_bar_click accepts 3 parameters: path, label, app_bundle_id. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for ui_menu_bar_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 Local. Nothing to install.
ui_menu_bar_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 ui_menu_bar_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 ui_menu_bar_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.
ui_menu_bar_click is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue