browser_refresh · Daytona Playwright MCP Server MCP

WHAT IT DOES

What browser_refresh does on Daytona Playwright MCP Server

AI agents invoke browser_refresh to trigger actions in Daytona Playwright 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 browser_refresh needs a policy

Refreshing a page is a browser action that executes an external operation. While typically benign, it can cause side effects such as re-submitting POST forms, re-triggering network requests, or disrupting ongoing interactions. It fits Execute as it triggers an external browser operation rather than simply reading or writing data.

From the tool's definition 'Refresh the current page' — triggers a browser navigation action that reloads the current page, which is an external operation with potential side effects (e.g., re-submitting forms, re-triggering requests).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_refresh Rate-limited

browser_refresh 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_refresh": {
      "limits": [
        {
          "counter": "browser_refresh_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 Daytona Playwright MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_refresh

What does the browser_refresh tool do? +

Refresh the current page. It is categorised as a Execute tool in the Daytona Playwright 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 browser_refresh? +

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

What risk level is browser_refresh? +

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

Can I rate-limit browser_refresh? +

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

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

browser_refresh is provided by the Daytona Playwright MCP Server MCP server (jamesmurdza/playwright-daytona-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.