AI agents invoke click_at 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.
Based on the server context which explicitly mentions simulated click interactions, 'click_at' almost certainly simulates a mouse click at a screen coordinate. This is an Execute-category action as it triggers UI interactions whose effects depend on arguments.
From the tool's definition Tool name 'click_at' on a server described as supporting 'simulated user interactions like clicks' for GUI testing
Documented attack patterns abuse exactly the kind of access click_at 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 click_at:
{
"version": "1",
"default": "deny",
"tools": {
"click_at": {
"limits": [
{
"counter": "click_at_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}click_at 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.
click_at. 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 click_at: 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.
click_at 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 click_at 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 click_at. 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.
click_at 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.