cloak_wait_for · CloakBrowser MCP Server MCP: Risk & Policy

WHAT IT DOES

What cloak_wait_for does on CloakBrowser MCP Server

AI agents invoke cloak_wait_for to trigger actions in CloakBrowser MCP Server. 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.

WHY IT NEEDS A POLICY

Why cloak_wait_for needs a policy

This tool is Execute-category because it triggers external operations (browser state monitoring and conditional page interactions) whose effects are argument-dependent. While it appears passive ('wait'), it actively monitors and responds to page state changes, which can trigger subsequent actions or conditionally activate other browser operations.

From the tool's definition Tool performs browser automation action ('Wait for an element or text to appear on the page') that triggers external operations on a Chromium instance.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cloak_wait_for Rate-limited

cloak_wait_for 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": {
    "cloak_wait_for": {
      "limits": [
        {
          "counter": "cloak_wait_for_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloakBrowser MCP Server, so you can run agents against it safely.

FAQ

Questions about cloak_wait_for

What does the cloak_wait_for tool do? +

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

How do I enforce a policy on cloak_wait_for? +

Register the CloakBrowser MCP Server MCP server in PolicyLayer and add a rule for cloak_wait_for: 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 CloakBrowser MCP Server. Nothing to install.

What risk level is cloak_wait_for? +

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

Can I rate-limit cloak_wait_for? +

Yes. Add a rate_limit block to the cloak_wait_for 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 cloak_wait_for completely? +

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

cloak_wait_for is provided by the CloakBrowser MCP Server MCP server (miwoomiwoo/cloakbrowser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.