auth_browser · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What auth_browser does on ServiceNow MCP Server

AI agents invoke auth_browser to trigger actions in ServiceNow 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 auth_browser needs a policy

This tool triggers an external browser operation and captures authentication cookies for future use. It actively launches a browser process and persists session credentials — this is an Execute-category action (browser action + external operation). Misuse could enable session hijacking or unauthorized access to the ServiceNow instance, hence medium severity.

From the tool's definition Launch browser for SSO authentication. Opens a browser window where you can log in with your enterprise SSO credentials. Cookies are captured and saved for subsequent API calls.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth_browser Rate-limited

auth_browser 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": {
    "auth_browser": {
      "limits": [
        {
          "counter": "auth_browser_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 ServiceNow MCP Server, so you can run agents against it safely.

FAQ

Questions about auth_browser

What does the auth_browser tool do? +

Launch browser for SSO authentication. Opens a browser window where you can log in with your enterprise SSO credentials. Cookies are captured and saved for subsequent API calls. Use this when you don. It is categorised as a Execute tool in the ServiceNow 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 auth_browser? +

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

What risk level is auth_browser? +

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

Can I rate-limit auth_browser? +

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

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

auth_browser is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.