AI agents invoke wait to trigger actions in DrissionPageMCP. 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 causes the browser automation to pause/wait for a specified number of seconds. It's an execution control action (timing/flow control) rather than a pure read or write. Misuse could cause delays but has minimal blast radius, hence low severity. Confidence is moderate because the description is minimal (Chinese: 'wait webpage for a seconds').
From the tool's definition '网页等待a秒' (wait webpage for a seconds) — triggers a timed pause in browser automation execution
Documented attack patterns abuse exactly the kind of access wait gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DrissionPageMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for wait:
{
"version": "1",
"default": "deny",
"tools": {
"wait": {
"limits": [
{
"counter": "wait_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wait 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.
网页等待a秒. It is categorised as a Execute tool in the DrissionPageMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DrissionPage MCP server in PolicyLayer and add a rule for 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 DrissionPageMCP. Nothing to install.
wait 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 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. 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 is provided by the DrissionPage MCP server (wxhzhwxhzh/drissionpagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 DrissionPageMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
37 DrissionPageMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.