AI agents invoke wait_minutes to trigger actions in Automagik Tools. 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 executes a blocking operation (sleep/delay) whose effects depend on the argument (number of minutes). While not destructive or financial, it can disrupt agent workflows by introducing arbitrary delays, potentially causing timeouts in dependent operations or preventing concurrent task completion.
From the tool's definition Tool name 'wait_minutes' with description 'Wait for specified minutes' indicates it triggers a time-delay operation that suspends execution flow.
Documented attack patterns abuse exactly the kind of access wait_minutes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_minutes:
{
"version": "1",
"default": "deny",
"tools": {
"wait_minutes": {
"limits": [
{
"counter": "wait_minutes_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wait_minutes 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.
Wait for specified minutes. It is categorised as a Execute tool in the Automagik Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for wait_minutes: 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 Automagik Tools. Nothing to install.
wait_minutes 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 wait_minutes 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 wait_minutes. 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.
wait_minutes is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, 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.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.