snow_trace_execution
Set up execution tracing configuration. Creates a trace session that scripts can write to. Use snow_get_script_output to retrieve trace data later.
This record as markdown: /tools/serac/snow-trace-execution.md
What snow_trace_execution does on Serac
AI agents use snow_trace_execution 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_trace_execution is rated Medium
This tool creates a persistent trace session in ServiceNow — a reversible data structure (can be modified or cleared later). While it enables visibility into script execution, the act of creating and configuring a trace session modifies system state. It is not destructive since trace sessions can be cleared/reconfigured.
From the tool's definition Tool name 'snow_trace_execution' and description states it 'Creates a trace session that scripts can write to', indicating creation of a configuration artifact.
Attacks that exploit this kind of access
The rule that runs snow_trace_execution 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_trace_execution, this is the rule to start with:
snow_trace_execution 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_trace_execution call is checked against it from then on.
Questions about snow_trace_execution
Set up execution tracing configuration. Creates a trace session that scripts can write to. Use snow_get_script_output to retrieve trace data later. 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_trace_execution: 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_trace_execution 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_trace_execution 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_trace_execution. 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_trace_execution 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