New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_script_include

Update a script include (requires SCRIPTING_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/update-script-include.md

What update_script_include does on ServiceNow-MCP

AI agents invoke update_script_include 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.

Why update_script_include is rated High

Updating a script include means changing executable server-side code in ServiceNow. This goes beyond a simple Write because the artifact being modified is executable code that runs in the platform context. A malicious or erroneous update could introduce arbitrary code execution across the ServiceNow instance, affecting all dependent processes.

From the tool's definition 'Update a script include' and 'requires SCRIPTING_ENABLED=true' — modifies server-side JavaScript code that executes within ServiceNow

Questions about update_script_include

What does the update_script_include tool do? +

Update a script include (requires SCRIPTING_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 update_script_include? +

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

What risk level is update_script_include? +

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

Can I rate-limit update_script_include? +

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.

How do I block update_script_include completely? +

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.

What MCP server provides update_script_include? +

update_script_include 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ServiceNow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.