switch_instance
Switch the active ServiceNow instance for this session
This record as markdown: /tools/servicenow-mcp-server/switch-instance.md
What switch_instance does on ServiceNow MCP Server
AI agents use switch_instance 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 switch_instance is rated Medium
This tool changes the active ServiceNow instance being used for the session. This is a configuration/state modification (Write) that could have high blast radius — an AI agent that switches instances could inadvertently redirect all subsequent operations (reads, writes, destructive actions) to a different environment (e.g., production instead of dev/test), potentially causing widespread unintended consequences.
From the tool's definition Switch the active ServiceNow instance for this session
Attacks that exploit this kind of access
The rule that runs switch_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For switch_instance, this is the rule to start with:
switch_instance 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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every switch_instance call is checked against it from then on.
Questions about switch_instance
Switch the active ServiceNow instance for this session. 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.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for switch_instance: 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.
switch_instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the switch_instance 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 switch_instance. 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.
switch_instance is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue