Get the currently active application scope on the ServiceNow instance.
AI agents call get_current_scope to retrieve information from Now Sdk Ext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about the active application scope on a ServiceNow instance. It performs no side effects, does not execute code, does not modify data, and does not delete anything. It is purely informational—a read operation querying system state. Low severity because knowing the current scope has minimal impact even if misused; it cannot directly harm data or trigger external actions.
From the tool's definition Tool name 'get_current_scope' and description 'Get the currently active application scope' indicate a query operation that retrieves configuration state without modification or execution.
Documented attack patterns abuse exactly the kind of access get_current_scope gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_scope:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_scope": {}
}
}get_current_scope is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the currently active application scope on the ServiceNow instance. It is categorised as a Read tool in the Now Sdk Ext MCP Server, which means it retrieves data without modifying state.
Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for 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 Now Sdk Ext. Nothing to install.
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 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 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.
get_current_scope is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Now Sdk Ext, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.