browser_close · AutoDev MCP: Risk & Policy

WHAT IT DOES

What browser_close does on AutoDev MCP

AI agents invoke browser_close to trigger actions in AutoDev MCP. 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_close needs a policy

Closing a browser session is an external operation that terminates a running process and triggers finalization of a persistent SQLite log entry. It is not purely destructive (no data deleted) nor a simple read/write — it executes a session lifecycle action with side effects on both the browser state and the database summary.

From the tool's definition 'Close browser session and finalize persisted summary' — terminates an active browser session and writes/finalizes a persisted summary record

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_close Rate-limited

browser_close 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_close": {
      "limits": [
        {
          "counter": "browser_close_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 AutoDev MCP, so you can run agents against it safely.

FAQ

Questions about browser_close

What does the browser_close tool do? +

Close browser session and finalize persisted summary. It is categorised as a Execute tool in the AutoDev MCP 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_close? +

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

What risk level is browser_close? +

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

Can I rate-limit browser_close? +

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

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

browser_close is provided by the AutoDev MCP server (rookiejefren/autocoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

browser_close is one line of AutoDev's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →