snow_backup_instance
Request a snapshot backup of the current ServiceNow instance under a chosen name, optionally including attachments. Returns the backup name and timestamp; the backup itself runs asynchronously.
This record as markdown: /tools/serac/snow-backup-instance.md
What snow_backup_instance does on Serac
AI agents use snow_backup_instance to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_backup_instance is rated Medium
This tool creates a new backup artifact (snapshot) which is a reversible operation—backups can be replaced or deleted later. While it has significant operational impact on system state and resources, it does not permanently delete data (ruling out Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).
From the tool's definition Creates a snapshot backup of the ServiceNow instance under a chosen name; specified as 'request a snapshot backup' which triggers data creation/capture rather than retrieval or destruction.
Attacks that exploit this kind of access
The rule that runs snow_backup_instance 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_backup_instance, this is the rule to start with:
snow_backup_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 Serac, apply this rule, and every snow_backup_instance call is checked against it from then on.
Questions about snow_backup_instance
Request a snapshot backup of the current ServiceNow instance under a chosen name, optionally including attachments. Returns the backup name and timestamp; the backup itself runs asynchronously. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_backup_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 Serac. Nothing to install.
snow_backup_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 snow_backup_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 snow_backup_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.
snow_backup_instance 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