run_transform_map
Execute a Transform Map on an Import Set to load data (requires WRITE_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/run-transform-map.md
What run_transform_map does on ServiceNow MCP Server
AI agents invoke run_transform_map to trigger actions in ServiceNow MCP Server. 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 run_transform_map is rated High
This tool runs a predefined transformation process on data, which constitutes code execution in the ServiceNow context. The effect is contingent on which Transform Map is executed and what data is present in the Import Set. While it modifies data (load data), it is categorized as Execute rather than Write because the primary action is triggering/running a transformation process.
From the tool's definition Tool executes a Transform Map on an Import Set to load data. The verb 'Execute' and the description 'Execute a Transform Map' indicate this triggers external operations whose effects depend on arguments.
Attacks that exploit this kind of access
The rule that runs run_transform_map 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 run_transform_map, this is the rule to start with:
run_transform_map 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 ServiceNow MCP Server, apply this rule, and every run_transform_map call is checked against it from then on.
Questions about run_transform_map
Execute a Transform Map on an Import Set to load data (requires WRITE_ENABLED=true). It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for run_transform_map: 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.
run_transform_map 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 run_transform_map 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 run_transform_map. 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.
run_transform_map 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.
Across the catalogue