Update an existing Script Include in ServiceNow.
AI agents use update_script_include to create or update resources in Snow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Snow environment.
Updating a Script Include modifies code stored in ServiceNow but does not delete or destroy data. Script Includes are executable code snippets used in ServiceNow workflows. While the update is reversible and doesn't permanently destroy data, it can affect system behavior if malicious code is injected.
From the tool's definition Tool name 'update_script_include' and description 'Update an existing Script Include in ServiceNow' indicate modification of existing data (Script Include objects) without deletion.
Documented attack patterns abuse exactly the kind of access update_script_include gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for update_script_include:
{
"version": "1",
"default": "deny",
"tools": {
"update_script_include": {
"limits": [
{
"counter": "update_script_include_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_script_include 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.
Free to start. No card required.
Update an existing Script Include in ServiceNow. It is categorised as a Write tool in the Snow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Snow MCP server in PolicyLayer and add a rule for update_script_include: 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 Snow. Nothing to install.
update_script_include 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 update_script_include 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 update_script_include. 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.
update_script_include is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.