snow_get_current_scope
Get the current application scope and active Update Set. 🔍 USE THIS TO: - Verify which scope you
This record as markdown: /tools/serac/snow-get-current-scope.md
What snow_get_current_scope does on Serac
AI agents call snow_get_current_scope to retrieve information from Serac without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why snow_get_current_scope is rated Low
This tool retrieves and verifies current state information (application scope and active Update Set) from ServiceNow. It performs no mutations, executions, or destructive operations. The blast radius of misuse is minimal—an attacker could only learn which scope is active, not alter anything or access sensitive data beyond scope metadata. This is a straightforward Read operation.
From the tool's definition Tool name 'snow_get_current_scope' and description 'Get the current application scope and active Update Set' indicate a read-only query operation that retrieves configuration information without modifying or executing any changes.
Attacks that exploit this kind of access
The rule that runs snow_get_current_scope safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_get_current_scope, this is the rule to start with:
snow_get_current_scope is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_get_current_scope call is checked against it from then on.
Questions about snow_get_current_scope
Get the current application scope and active Update Set. 🔍 USE THIS TO: - Verify which scope you. 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_get_current_scope: 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_get_current_scope 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_get_current_scope 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_get_current_scope. 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_get_current_scope 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.
More on Serac, and thousands of servers like it.
This server
Across the catalogue