auth_import_cookies · ServiceNow MCP Server MCP

WHAT IT DOES

What auth_import_cookies does on ServiceNow MCP Server

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

WHY IT NEEDS A POLICY

Why auth_import_cookies needs a policy

This tool writes/injects authentication state (session cookies and user tokens) into the MCP server. It doesn't read data or destroy it, but it modifies the authentication context of the running session, which could allow an attacker to hijack a privileged ServiceNow session.

From the tool's definition Import authentication cookies from an external source... transfer those credentials to the MCP. Extract cookies and x-usertoken from network request headers.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth_import_cookies Rate-limited

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

FAQ

Questions about auth_import_cookies

What does the auth_import_cookies tool do? +

Import authentication cookies from an external source. Use this when you already have an authenticated browser session (e.g., via Firefox DevTools) and want to transfer those credentials to the MCP. Extract cookies and x-usertoken from network request headers. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on auth_import_cookies? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for auth_import_cookies: 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_import_cookies? +

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

Can I rate-limit auth_import_cookies? +

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

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

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