Dump the current ServiceNow session context for the authenticated user: sys_id, username, email, roles (with inherited flag), current update set, domain, timezone, locale. One call instead of 3-4 scattered queries. Use this to ground ACL / role-based reasoning before running a script or diagnosin...
AI agents call snow_session_context to retrieve information from Serac without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves session information (identity, roles, email, locale, etc.) with no side effects. However, the data exposed—user sys_id, email, roles, current update set—is sensitive identity and permission metadata that could be leveraged for privilege escalation or targeted attacks if misused, warranting a medium severity rating.
From the tool's definition Dump the current ServiceNow session context...sys_id, username, email, roles (with inherited flag), current update set, domain, timezone, locale. One call instead of 3-4 scattered queries.
Attacks that exploit this kind of access
Dump the current ServiceNow session context for the authenticated user: sys_id, username, email, roles (with inherited flag), current update set, domain, timezone, locale. One call instead of 3-4 scattered queries. Use this to ground ACL / role-based reasoning before running a script or diagnosing permissions. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.
Register the Serac MCP server in PolicyLayer and add a rule for snow_session_context: 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 Serac. Nothing to install.
snow_session_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the snow_session_context 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.
Set action: deny in the PolicyLayer policy for snow_session_context. 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.
snow_session_context is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
snow_session_context is one line of Serac'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 →