browser_save_session · Universal Dev MCP: Risk & Policy

WHAT IT DOES

What browser_save_session does on Universal Dev MCP

AI agents use browser_save_session to create or update resources in Universal Dev MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Universal Dev MCP environment.

WHY IT NEEDS A POLICY

Why browser_save_session needs a policy

Saving session cookies to disk is a Write operation—it creates or modifies stored data (session files) reversibly. This is not destructive since the operation can be reversed (session files can be deleted or overwritten).

From the tool's definition Tool name 'browser_save_session' and description 'save [browser session/cookies] disk par' indicates writing session data to disk.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_save_session Rate-limited

browser_save_session stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_save_session": {
      "limits": [
        {
          "counter": "browser_save_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Universal Dev MCP, so you can run agents against it safely.

FAQ

Questions about browser_save_session

What does the browser_save_session tool do? +

Current browser session (cookies) disk par save karo. It is categorised as a Write tool in the Universal Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_save_session? +

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

What risk level is browser_save_session? +

browser_save_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_save_session? +

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

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

browser_save_session is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.