This record as markdown: /tools/serac/snow-transform-data.md
What snow_transform_data does on Serac
AI agents invoke snow_transform_data to trigger actions in Serac. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why snow_transform_data is rated High
While 'transform' could seem like a write operation, the description indicates it executes transformation logic using field mappings rather than simply creating/modifying discrete records. This constitutes code execution on data.
From the tool's definition Tool performs data transformation using field mappings, which involves executing transformation logic against data. In a ServiceNow context with 400+ MCP tools, this operates on enterprise data structures and field configurations.
Attacks that exploit this kind of access
The rule that runs snow_transform_data 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_transform_data, this is the rule to start with:
snow_transform_data stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_transform_data call is checked against it from then on.
Questions about snow_transform_data
Transform data using field mappings. It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Serac MCP server in PolicyLayer and add a rule for snow_transform_data: 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_transform_data is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the snow_transform_data 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_transform_data. 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_transform_data 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.
Across the catalogue