AI agents invoke confirm to trigger actions in PyMCPAutoGUI. 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.
Given the server context of GUI automation and sibling tools like 'alert', 'confirm' almost certainly displays a confirmation dialog box and returns the user's response — a GUI interaction/execution action. However, the description is empty, so confidence is reduced. It could trigger UI interactions with side effects depending on what is confirmed.
From the tool's definition Tool name 'confirm' on a GUI automation server (PyMCPAutoGUI) that controls mouse, keyboard, windows, and desktop applications. Sibling tools include alert, click, drag, activate_window, etc.
Documented attack patterns abuse exactly the kind of access confirm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PyMCPAutoGUI, and nothing reaches the server without passing your rules. This is the rule we recommend for confirm:
{
"version": "1",
"default": "deny",
"tools": {
"confirm": {
"limits": [
{
"counter": "confirm_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}confirm 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.
confirm. It is categorised as a Execute tool in the PyMCPAutoGUI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PyMCPAutoGUI MCP server in PolicyLayer and add a rule for confirm: 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 PyMCPAutoGUI. Nothing to install.
confirm 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 confirm 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 confirm. 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.
confirm is provided by the PyMCPAutoGUI MCP server (kitfactory/pymcpautogui). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PyMCPAutoGUI, 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.
34 PyMCPAutoGUI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.