run_transform_map

Execute a Transform Map on an Import Set to load data (requires WRITE_ENABLED=true)

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/run-transform-map.md

WHAT IT DOES

What run_transform_map does on ServiceNow-MCP

AI agents invoke run_transform_map to trigger actions in ServiceNow-MCP. 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.

RISK

Why run_transform_map is rated High

This tool runs a Transform Map, which is an operational process that executes logic to load and transform data from an Import Set into ServiceNow tables. While nominally a 'Write' operation (data loading), Transform Maps execute arbitrary transformation logic defined by administrators, making the effects highly dependent on the map's configuration and input data.

From the tool's definition Execute a Transform Map on an Import Set to load data (requires WRITE_ENABLED=true)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_transform_map safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_transform_map": {
      "limits": [
        {
          "counter": "run_transform_map_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every run_transform_map call is checked against it from then on.

FAQ

Questions about run_transform_map

What does the run_transform_map tool do? +

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 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_transform_map? +

Register the ServiceNow 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. Nothing to install.

What risk level is run_transform_map? +

run_transform_map is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_transform_map? +

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.

How do I block run_transform_map completely? +

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.

What MCP server provides run_transform_map? +

run_transform_map is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →