This record as markdown: /tools/0xcarbon-qt-mcp/qt-menu-items.md
What qt_menu_items does on Qt
AI agents call qt_menu_items to retrieve information from Qt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why qt_menu_items is rated Low
This tool retrieves and inspects the list of menu items/actions available in a QMenu widget. It does not execute any actions, modify the menu, delete entries, or interact with external systems. It is purely introspective—suitable for an AI agent to understand UI structure before deciding what action to take.
From the tool's definition Tool name 'qt_menu_items' and description 'Get actions from a QMenu widget' — both indicate data retrieval with no modification or execution. 'Get' is explicitly a read operation; querying a menu's available actions produces no side effects.
Attacks that exploit this kind of access
The rule that runs qt_menu_items safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Qt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For qt_menu_items, this is the rule to start with:
qt_menu_items is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Qt, apply this rule, and every qt_menu_items call is checked against it from then on.
Questions about qt_menu_items
Get actions from a QMenu widget. It is categorised as a Read tool in the Qt MCP Server, which means it retrieves data without modifying state.
Register the Qt MCP server in PolicyLayer and add a rule for qt_menu_items: 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 Qt. Nothing to install.
qt_menu_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the qt_menu_items 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 qt_menu_items. 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.
qt_menu_items is provided by the Qt MCP server (0xcarbon/qt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Qt, and thousands of servers like it.
This server
Across the catalogue