Executes a Unity Editor menu item (e.g. 'Assets/Refresh', 'Window/General/Game').
AI agents invoke execute_menu_item to trigger actions in MCP For Unity. 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 allows execution of arbitrary Unity Editor menu commands, which can have significant side effects depending on the menu item selected (e.g., 'Assets/Build', 'Tools/Refresh', custom plugin menus). While some menu items are read-only, the tool's design permits triggering code execution, asset modifications, and external processes.
From the tool's definition Tool name 'execute_menu_item' combined with description 'Executes a Unity Editor menu item' indicates arbitrary invocation of menu commands.
Attacks that exploit this kind of access
Executes a Unity Editor menu item (e.g. 'Assets/Refresh', 'Window/General/Game'). It is categorised as a Execute tool in the MCP For Unity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP For Unity MCP server in PolicyLayer and add a rule for execute_menu_item: 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 MCP For Unity. Nothing to install.
execute_menu_item 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 execute_menu_item 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 execute_menu_item. 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.
execute_menu_item is provided by the MCP For Unity MCP server (yunuscan/mcpforunity). 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 →