AI agents invoke press_key to trigger actions in Qt Pilot. 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 simulates keyboard input on a running desktop application. Depending on the key pressed (e.g., Enter, Delete, Ctrl+S), it can trigger significant application actions. It is an active interaction/execution against an external application, not merely reading data or writing structured content.
From the tool's definition Simulate a key press
Documented attack patterns abuse exactly the kind of access press_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qt Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for press_key:
{
"version": "1",
"default": "deny",
"tools": {
"press_key": {
"limits": [
{
"counter": "press_key_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}press_key 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.
Free to start. No card required.
Simulate a key press. It is categorised as a Execute tool in the Qt Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qt Pilot MCP server in PolicyLayer and add a rule for press_key: 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 Pilot. Nothing to install.
press_key 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 press_key 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 press_key. 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.
press_key is provided by the Qt Pilot MCP server (neatobandit0/qt-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Qt Pilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Qt Pilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.