auth_refresh · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What auth_refresh does on ServiceNow MCP Server

AI agents invoke auth_refresh 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_refresh needs a policy

This tool triggers an external browser-based authentication operation. It doesn't merely read data or write records — it actively initiates a browser session/re-authentication flow, which is an external operation whose effects depend on the current session state. Misuse could result in unintended session changes or authentication disruptions, warranting a medium severity rating.

From the tool's definition 'Refresh the current session by re-authenticating via browser' and 'Uses the previously authenticated instance URL'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth_refresh Rate-limited

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

FAQ

Questions about auth_refresh

What does the auth_refresh tool do? +

Refresh the current session by re-authenticating via browser. Uses the previously authenticated instance URL. Useful when session has expired. 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_refresh? +

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

What risk level is auth_refresh? +

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

Can I rate-limit auth_refresh? +

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

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

auth_refresh 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.