iframe-click-element

A execute tool on the AdsPower LocalAPI MCP server.

SERVERAdsPower LocalAPI MCP Server SOURCEadspower/adspower-browser

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/adspower-adspower-browser/iframe-click-element.md

WHAT IT DOES

What iframe-click-element does on AdsPower LocalAPI MCP Server

AI agents invoke iframe-click-element to trigger actions in AdsPower LocalAPI 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.

RISK

Why iframe-click-element is rated High

The tool name implies a browser action (clicking an element inside an iframe), which falls under Execute as it triggers UI interactions in an external browser. Sibling tools confirm this is a browser automation server. However, the description is empty, so confidence is reduced. Clicking can have wide-ranging effects depending on what is clicked, hence high severity.

From the tool's definition Tool name 'iframe-click-element' suggests clicking an element within an iframe in a browser context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs iframe-click-element safely

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

iframe-click-element Rate-limited

iframe-click-element 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": {
    "iframe-click-element": {
      "limits": [
        {
          "counter": "iframe-click-element_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 AdsPower LocalAPI MCP Server, apply this rule, and every iframe-click-element call is checked against it from then on.

FAQ

Questions about iframe-click-element

What does the iframe-click-element tool do? +

iframe-click-element is a execute tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Execute tool in the AdsPower LocalAPI 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 iframe-click-element? +

Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for iframe-click-element: 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 AdsPower LocalAPI MCP Server. Nothing to install.

What risk level is iframe-click-element? +

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

Can I rate-limit iframe-click-element? +

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

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

iframe-click-element is provided by the AdsPower LocalAPI MCP Server MCP server (adspower/adspower-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AdsPower LocalAPI MCP Server, and thousands of servers like it.

This server

All 47 AdsPower LocalAPI MCP Server tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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