browser_only_tool

Tool only available in browser runtime (should be filtered)

SERVERFrontmcp SOURCEagentfront/frontmcp

Low RISK CLASS

Category Other

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-only-tool.md

WHAT IT DOES

What browser_only_tool does on Frontmcp

AI agents call browser_only_tool as a supporting operation in Frontmcp workflows.

RISK

Why browser_only_tool is rated Low

The description indicates this tool is meant to be filtered out and only available in browser runtime. There is no information about what the tool actually does, making it impossible to classify its action. The parenthetical '(should be filtered)' suggests it may not even be accessible in the current context. Confidence is low due to the uninformative description.

From the tool's definition Tool only available in browser runtime (should be filtered)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_only_tool 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_only_tool, this is the rule to start with:

browser_only_tool Rate-limited

browser_only_tool gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_only_tool": {
      "limits": [
        {
          "counter": "browser_only_tool_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every browser_only_tool call is checked against it from then on.

FAQ

Questions about browser_only_tool

What does the browser_only_tool tool do? +

Tool only available in browser runtime (should be filtered). It is categorised as a Other tool in the Frontmcp MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on browser_only_tool? +

Register the Front MCP server in PolicyLayer and add a rule for browser_only_tool: 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_only_tool? +

browser_only_tool is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_only_tool? +

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

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

browser_only_tool 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 →

Across the catalogue

async_tool on Enhanced Image Analysis MCP Server →my_tool on Agentic Automl Platform →async_tool on IaC Memory MCP Server →async_tool on Optimized Memory MCP Server V2 → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →