browser_iframe_click

A execute tool on the Termux Browser Pilot MCP server.

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot

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/salviz-termux-browser-pilot/browser-iframe-click.md

WHAT IT DOES

What browser_iframe_click does on Termux Browser Pilot

AI agents invoke browser_iframe_click to trigger actions in Termux Browser Pilot. 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 browser_iframe_click is rated High

The tool name indicates clicking within an iframe in a real browser automation context. Clicking triggers external operations (form submissions, navigation, JavaScript events, purchases, etc.) whose effects depend on the target element. The server description confirms real browser automation with persistent daemon.

From the tool's definition Tool name: browser_iframe_click; server is a browser automation platform running real Firefox/Chromium

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_iframe_click safely

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

browser_iframe_click Rate-limited

browser_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": {
    "browser_iframe_click": {
      "limits": [
        {
          "counter": "browser_iframe_click_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 Termux Browser Pilot, apply this rule, and every browser_iframe_click call is checked against it from then on.

FAQ

Questions about browser_iframe_click

What does the browser_iframe_click tool do? +

browser_iframe_click is a execute tool on the Termux Browser Pilot MCP server. It is categorised as a Execute tool in the Termux Browser Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_iframe_click? +

Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_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 Termux Browser Pilot. Nothing to install.

What risk level is browser_iframe_click? +

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

Can I rate-limit browser_iframe_click? +

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

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

browser_iframe_click is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Termux Browser Pilot, and thousands of servers like it.

This server

All 148 Termux Browser Pilot 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 →