push_artifact
Local sync: write edited fields back to an artifact (requires WRITE_ENABLED=true). Pass fields inline as {field:value}; if omitted and NOWAIKIT_SYNC_DIR is set, reads them from the pulled files on disk. Overwrites the listed fields with NO merge — run sync_status first, and pass expected_updated_...
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/push-artifact.md
What push_artifact does on NowAIKit — ServiceNow AI Toolkit
AI agents use push_artifact 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 push_artifact is rated Medium
This tool creates or modifies data reversibly by writing/overwriting fields on ServiceNow artifacts. While it modifies existing records, it does not delete or irreversibly destroy data (making it Write rather than Destructive).
From the tool's definition Tool description explicitly states it "write[s] edited fields back to an artifact" and "Overwrites the listed fields". The phrase "requires WRITE_ENABLED=true" confirms it performs write operations.
Attacks that exploit this kind of access
The rule that runs push_artifact 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 push_artifact, this is the rule to start with:
push_artifact 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 push_artifact call is checked against it from then on.
Questions about push_artifact
Local sync: write edited fields back to an artifact (requires WRITE_ENABLED=true). Pass fields inline as {field:value}; if omitted and NOWAIKIT_SYNC_DIR is set, reads them from the pulled files on disk. Overwrites the listed fields with NO merge — run sync_status first, and pass expected_updated_on to abort if the instance changed since you pulled. 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 push_artifact: 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.
push_artifact 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 push_artifact 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 push_artifact. 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.
push_artifact 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