browser_test

A tool defined in the browser

SERVERFrontmcp SOURCEagentfront/frontmcp

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/frontmcp/browser-test.md

WHAT IT DOES

What browser_test does on Frontmcp

AI agents invoke browser_test to trigger actions in Frontmcp. 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_test is rated High

The tool name 'browser_test' combined with 'defined in the browser' strongly suggests this tool runs or interacts with a browser environment, which falls under Execute. Browser automation can trigger arbitrary web actions, navigate pages, submit forms, or execute scripts. The description is vague, which lowers confidence, but the browser execution context implies significant blast radius if misused.

From the tool's definition 'A tool defined in the browser' — name 'browser_test' implies browser execution/automation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_test safely

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

browser_test Rate-limited

browser_test 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_test": {
      "limits": [
        {
          "counter": "browser_test_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 Frontmcp, apply this rule, and every browser_test call is checked against it from then on.

FAQ

Questions about browser_test

What does the browser_test tool do? +

A tool defined in the browser. It is categorised as a Execute tool in the Frontmcp 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_test? +

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

What risk level is browser_test? +

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

Can I rate-limit browser_test? +

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

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

browser_test is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools → High-risk tools on this server →

Across the catalogue

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

Guides

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