import_excel_to_import_set
Upload and parse one .xlsx worksheet, create an Import Set, insert its staging rows, and optionally run a Transform Map.
This record as markdown: /tools/tedorigawa001-servicenow-mcp/import-excel-to-import-set.md
What import_excel_to_import_set does on ServiceNow-MCP
AI agents use import_excel_to_import_set to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Why import_excel_to_import_set is rated Medium
Creates and modifies data in ServiceNow staging and potentially target tables through import transformation.
From the tool's definition Upload, create Import Set, insert staging rows, optionally run Transform Map.
Attacks that exploit this kind of access
The rule that runs import_excel_to_import_set 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 import_excel_to_import_set, this is the rule to start with:
import_excel_to_import_set 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 ServiceNow-MCP, apply this rule, and every import_excel_to_import_set call is checked against it from then on.
Questions about import_excel_to_import_set
Upload and parse one .xlsx worksheet, create an Import Set, insert its staging rows, and optionally run a Transform Map. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP server in PolicyLayer and add a rule for import_excel_to_import_set: 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.
import_excel_to_import_set 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 import_excel_to_import_set 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 import_excel_to_import_set. 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.
import_excel_to_import_set 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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue