AI agents invoke wait_for_selector to trigger actions in Mcp Playwright. 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 browser automation action (waiting/polling for element availability) whose effects depend on the selector argument and page state. While not as severe as 'click_element' or 'execute_javascript', it still represents code execution that can hang, timeout, or affect downstream actions.
From the tool's definition Tool is part of a browser automation suite (Playwright) that performs actions with side effects. 'wait_for_selector' waits for DOM elements to appear, which is a blocking operation that controls browser behavior and execution flow.
Documented attack patterns abuse exactly the kind of access wait_for_selector gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Playwright, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_for_selector:
{
"version": "1",
"default": "deny",
"tools": {
"wait_for_selector": {
"limits": [
{
"counter": "wait_for_selector_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wait_for_selector 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.
等待元素出现. It is categorised as a Execute tool in the Mcp Playwright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Playwright MCP server in PolicyLayer and add a rule for wait_for_selector: 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 Mcp Playwright. Nothing to install.
wait_for_selector 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_for_selector 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_for_selector. 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_for_selector is provided by the Mcp Playwright MCP server (ma-pony/mcp-playwright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Playwright, 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.
12 Mcp Playwright tools catalogued and risk-classified — across an index of 43,000+ MCP servers.