// MCP TOOL REFERENCE

QT PILOT TOOLS

15 tools from the Qt Pilot MCP Server, categorised by risk level.

// ALL 15 QT PILOT TOOLS

READ 6 tools

Read capture_screenshot Capture screenshot of current application. Read find_widgets List widgets matching a name pattern. Read get_app_status Check if the application is still running and get diagnostics. Read get_widget_info Get detailed information about a specific widget. Read list_actions List all QActions in the application. Read list_all_widgets list_all_widgets

DESTRUCTIVE 1 tools

Destructive close_app Close the currently running application.

EXECUTE 8 tools

Execute launch_app launch_app Execute trigger_action Trigger a QAction by its object name. Execute wait_for_idle Wait for the Qt application to process pending events. Execute hover_widget Hover over a widget by its object name. Execute click_at click_at Execute click_widget Click a widget by its object name. Execute press_key Simulate a key press. Execute type_text Type text into a widget or the currently focused widget.

// FAQ

How many tools does the Qt Pilot MCP server have? +

The Qt Pilot MCP server exposes 15 tools across 3 categories: Read, Destructive, Execute.

How do I enforce policies on Qt Pilot tools? +

Route the Qt Pilot server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Qt Pilot tools fall into? +

Qt Pilot tools are categorised as Read (6), Destructive (1), Execute (8). Each category has a recommended default policy.

Enforce policy on every Qt Pilot tool call.

Start from Qt Pilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.