AI agents call delay as a supporting operation in uiautomator2 MCP Server workflows.
The name 'delay' suggests a pause or wait operation with no side effects, which doesn't clearly fit Read, Write, Execute, Destructive, Financial, or other impactful categories. With no description available, confidence is low, but a delay/sleep function is typically a timing utility with minimal blast radius.
From the tool's definition Tool name is 'delay' and description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access delay gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delay:
{
"version": "1",
"default": "deny",
"tools": {
"delay": {
"limits": [
{
"counter": "delay_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}delay gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
delay. It is categorised as a Other tool in the uiautomator2 MCP Server MCP Server, which means it performs auxiliary operations.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for delay: 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 uiautomator2 MCP Server. Nothing to install.
delay 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 delay 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 delay. 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.
delay is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 MCP Server, 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.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.