bulk_create_records
Create many records in one table in a single call, tracking every created sys_id and returning a rollback_token. With rollback_on_error=true, a mid-way failure deletes everything already created so the batch is all-or-nothing. Supports dry_run. Requires WRITE_ENABLED=true.
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/bulk-create-records.md
What bulk_create_records does on NowAIKit — ServiceNow AI Toolkit
AI agents use bulk_create_records to create or update resources in NowAIKit — ServiceNow AI Toolkit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NowAIKit — ServiceNow AI Toolkit environment.
Why bulk_create_records is rated Medium
This tool creates data reversibly (records can be deleted or modified later). While it operates in bulk and has high blast radius if misused by an agent (creating many unwanted records), it does not irreversibly destroy data (Destructive), execute arbitrary code (Execute), or move money (Financial). The rollback capability and dry_run support confirm data integrity controls exist.
From the tool's definition Tool description explicitly states 'Create many records in one table in a single call' and 'Requires WRITE_ENABLED=true'. The bulk nature and all-or-nothing semantics with rollback capability indicate write operations at scale.
Attacks that exploit this kind of access
The rule that runs bulk_create_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NowAIKit — ServiceNow AI Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_create_records, this is the rule to start with:
bulk_create_records 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 NowAIKit — ServiceNow AI Toolkit, apply this rule, and every bulk_create_records call is checked against it from then on.
Questions about bulk_create_records
Create many records in one table in a single call, tracking every created sys_id and returning a rollback_token. With rollback_on_error=true, a mid-way failure deletes everything already created so the batch is all-or-nothing. Supports dry_run. Requires WRITE_ENABLED=true. It is categorised as a Write tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NowAIKit — ServiceNow AI Toolkit MCP server in PolicyLayer and add a rule for bulk_create_records: 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 NowAIKit — ServiceNow AI Toolkit. Nothing to install.
bulk_create_records 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 bulk_create_records 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 bulk_create_records. 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.
bulk_create_records is provided by the NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.
This server
Across the catalogue