browser_template_apply · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What browser_template_apply does on Claude Flow

AI agents invoke browser_template_apply to trigger actions in Claude Flow. 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 browser_template_apply needs a policy

The tool fetches a recipe/template and triggers browser automation execution including login flows, cookie reuse, and DOM interaction. 'Caller-level execution' and 'login flows with cookie reuse' indicate active session-bearing browser operations that can interact with authenticated web services, scrape sensitive content, or execute arbitrary automation scripts.

From the tool's definition 'real browser automation', 'JS-heavy SPA scraping, login flows with cookie reuse, replay against DOM-drifted versions', 'caller-level execution'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_template_apply Rate-limited

browser_template_apply 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_template_apply": {
      "limits": [
        {
          "counter": "browser_template_apply_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 Claude Flow, so you can run agents against it safely.

FAQ

Questions about browser_template_apply

What does the browser_template_apply tool do? +

Fetch a recipe from the browser-templates AgentDB namespace and return it for caller-level execution. Use when native WebFetch is wrong because you need real browser automation — JS-heavy SPA scraping, login flows with cookie reuse, replay against DOM-drifted versions, AIDefence PII gating before content reaches Claude. For static HTML pages, native WebFetch is faster and free. It is categorised as a Execute tool in the Claude Flow 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_template_apply? +

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

What risk level is browser_template_apply? +

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

Can I rate-limit browser_template_apply? +

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

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

browser_template_apply is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.