Sets the pause duration (in seconds) between each pyautogui function call.
AI agents use set_pause to create or update resources in PyMCPAutoGUI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PyMCPAutoGUI environment.
This tool modifies a configuration/behavioral setting (inter-call pause duration) of the automation framework. It doesn't read data, execute commands, delete anything, or involve finances. It's a reversible configuration change, hence Write. Misuse potential is low — changing pause timing could affect automation behavior but has minimal blast radius on its own.
From the tool's definition Sets the pause duration (in seconds) between each pyautogui function call
Documented attack patterns abuse exactly the kind of access set_pause 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 set_pause:
{
"version": "1",
"default": "deny",
"tools": {
"set_pause": {
"limits": [
{
"counter": "set_pause_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_pause stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Sets the pause duration (in seconds) between each pyautogui function call. It is categorised as a Write tool in the PyMCPAutoGUI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PyMCPAutoGUI MCP server in PolicyLayer and add a rule for set_pause: 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.
set_pause is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_pause 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 set_pause. 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.
set_pause 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.