page_wait_for_selector

Wait for an element to appear.

SERVERJshookmcp SOURCE@jshookmcp/jshook

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/page-wait-for-selector.md

WHAT IT DOES

What page_wait_for_selector does on Jshookmcp

AI agents invoke page_wait_for_selector to trigger actions in Jshookmcp. 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.

RISK

Why page_wait_for_selector is rated High

Browser automation tool that triggers external operations with unpredictable effects dependent on page state and selectors.

From the tool's definition Wait for element to appear; browser automation capability

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs page_wait_for_selector safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For page_wait_for_selector, this is the rule to start with:

page_wait_for_selector Rate-limited

page_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "page_wait_for_selector": {
      "limits": [
        {
          "counter": "page_wait_for_selector_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every page_wait_for_selector call is checked against it from then on.

FAQ

Questions about page_wait_for_selector

What does the page_wait_for_selector tool do? +

Wait for an element to appear. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on page_wait_for_selector? +

Register the Jshook MCP server in PolicyLayer and add a rule for page_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 Jshookmcp. Nothing to install.

What risk level is page_wait_for_selector? +

page_wait_for_selector is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit page_wait_for_selector? +

Yes. Add a rate_limit block to the page_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.

How do I block page_wait_for_selector completely? +

Set action: deny in the PolicyLayer policy for page_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.

What MCP server provides page_wait_for_selector? +

page_wait_for_selector is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → High-risk tools on this server →

Across the catalogue

browser_wait_for_element on Percepta MCP Server →wait_for_renders on Why Did You Render →qt_wait_for on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →