refresh_page · Brave Browser MCP Server MCP: Risk & Policy

WHAT IT DOES

What refresh_page does on Brave Browser MCP Server

AI agents invoke refresh_page to trigger actions in Brave Browser 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.

WHY IT NEEDS A POLICY

Why refresh_page needs a policy

Refreshing a page is an external operation that re-executes a network request and re-renders the page. It has no direct destructive or financial impact, but it does trigger a real browser action with potential side effects (e.g., re-submitting forms, re-running page scripts). It falls under Execute as it triggers an external operation in the browser environment.

From the tool's definition "Reloads the current page" — triggers an external browser operation (HTTP request/page reload)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_page Rate-limited

refresh_page 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": {
    "refresh_page": {
      "limits": [
        {
          "counter": "refresh_page_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 Brave Browser MCP Server, so you can run agents against it safely.

FAQ

Questions about refresh_page

What does the refresh_page tool do? +

Reloads the current page. It is categorised as a Execute tool in the Brave Browser 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 refresh_page? +

Register the Brave Browser MCP Server MCP server in PolicyLayer and add a rule for refresh_page: 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 Brave Browser MCP Server. Nothing to install.

What risk level is refresh_page? +

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

Can I rate-limit refresh_page? +

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

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

refresh_page is provided by the Brave Browser MCP Server MCP server (slaveofgod1/brave-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.