execute_menu_item
AI agents invoke execute_menu_item to trigger actions in GameDevBench 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.
This tool triggers menu actions in Godot, which can execute arbitrary game engine operations—including running code, modifying project state, launching builds, or invoking plugins. The effects are determined by the menu item argument and cannot be safely sandboxed.
From the tool's definition Tool name 'execute_menu_item' indicates it triggers menu actions within Godot. Combined with server context showing AppleScript-based automation and sibling tools like 'execute_blender_code' and 'create_script', this tool executes external operations with…
Attacks that exploit this kind of access
execute_menu_item. It is categorised as a Execute tool in the GameDevBench MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GameDevBench 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 GameDevBench MCP. 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 GameDevBench MCP server (seeleai/gamedevbench-mcp). 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 →