playwright_iframe_click · Playwright MCP Server MCP

WHAT IT DOES

What playwright_iframe_click does on Playwright MCP Server

AI agents invoke playwright_iframe_click to trigger actions in Playwright 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 playwright_iframe_click needs a policy

Clicking elements in iframes can trigger form submissions, navigation, purchases, downloads, or other operations with real-world consequences. The effect depends entirely on the target element, making this an Execute-category action with high blast radius since iframes often host third-party content, payment widgets, or authentication flows.

From the tool's definition 'Click an element in an iframe on the page' — triggers a browser click action inside an iframe, causing external side effects depending on what the element does

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

playwright_iframe_click Rate-limited

playwright_iframe_click 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": {
    "playwright_iframe_click": {
      "limits": [
        {
          "counter": "playwright_iframe_click_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 Playwright MCP Server, so you can run agents against it safely.

FAQ

Questions about playwright_iframe_click

What does the playwright_iframe_click tool do? +

Click an element in an iframe on the page. It is categorised as a Execute tool in the Playwright 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 playwright_iframe_click? +

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

What risk level is playwright_iframe_click? +

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

Can I rate-limit playwright_iframe_click? +

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

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

playwright_iframe_click is provided by the Playwright MCP Server MCP server (vinothbhc1986/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

playwright_iframe_click is one line of Playwright MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →