qt_key_press

Send a key event to a widget or the focused widget.

SERVERQt SOURCE0xcarbon/qt-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xcarbon-qt-mcp/qt-key-press.md

WHAT IT DOES

What qt_key_press does on Qt

AI agents invoke qt_key_press to trigger actions in Qt. 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.

RISK

Why qt_key_press is rated High

This tool triggers external operations by sending keyboard input to a running desktop application. The effects depend on which widget receives the key event and what keys are sent — it could submit forms, trigger shortcuts, or navigate UI elements. This qualifies as Execute since it performs browser/UI actions whose impact depends on arguments.

From the tool's definition Send a key event to a widget or the focused widget

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs qt_key_press 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_key_press, this is the rule to start with:

qt_key_press Rate-limited

qt_key_press 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qt_key_press": {
      "limits": [
        {
          "counter": "qt_key_press_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Qt, apply this rule, and every qt_key_press call is checked against it from then on.

FAQ

Questions about qt_key_press

What does the qt_key_press tool do? +

Send a key event to a widget or the focused widget. It is categorised as a Execute tool in the Qt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on qt_key_press? +

Register the Qt MCP server in PolicyLayer and add a rule for qt_key_press: 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.

What risk level is qt_key_press? +

qt_key_press is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit qt_key_press? +

Yes. Add a rate_limit block to the qt_key_press 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.

How do I block qt_key_press completely? +

Set action: deny in the PolicyLayer policy for qt_key_press. 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.

What MCP server provides qt_key_press? +

qt_key_press 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.

KEEP EXPLORING

More on Qt, and thousands of servers like it.

This server

All 24 Qt tools → High-risk tools on this server →

Across the catalogue

send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →