AI agents call omniparser_wait as a supporting operation in Omniparser Autogui workflows.
This tool simply introduces a time delay and has no side effects — it does not read, write, execute, destroy, or move money. It is a timing/synchronization utility, genuinely falling into the 'Other' category with minimal blast radius.
From the tool's definition Waits for the specified number of seconds
Documented attack patterns abuse exactly the kind of access omniparser_wait gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Omniparser Autogui, and nothing reaches the server without passing your rules. This is the rule we recommend for omniparser_wait:
{
"version": "1",
"default": "deny",
"tools": {
"omniparser_wait": {
"limits": [
{
"counter": "omniparser_wait_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}omniparser_wait gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Waits for the specified number of seconds. It is categorised as a Other tool in the Omniparser Autogui MCP Server, which means it performs auxiliary operations.
Register the Omniparser Autogui MCP server in PolicyLayer and add a rule for omniparser_wait: 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 Omniparser Autogui. Nothing to install.
omniparser_wait is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the omniparser_wait 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 omniparser_wait. 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.
omniparser_wait is provided by the Omniparser Autogui MCP server (non906/omniparser-autogui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Omniparser Autogui tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Omniparser Autogui tools catalogued and risk-classified — across an index of 42,500+ MCP servers.