create_script_include
Create a new script include (requires SCRIPTING_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/create-script-include.md
What create_script_include does on ServiceNow MCP Server
AI agents invoke create_script_include to trigger actions in ServiceNow MCP Server. 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 create_script_include is rated High
Creating a script include stores and enables execution of arbitrary server-side JavaScript in the ServiceNow platform. Although the act of creation is a Write, the payload is executable code that can be triggered by other scripts and server processes, making this effectively an Execute-category action. Misuse could introduce malicious server-side logic with broad blast radius across the platform.
From the tool's definition 'Create a new script include' — script includes are server-side JavaScript code that can be invoked by other scripts; requires SCRIPTING_ENABLED=true
Attacks that exploit this kind of access
The rule that runs create_script_include safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_script_include, this is the rule to start with:
create_script_include stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 Server, apply this rule, and every create_script_include call is checked against it from then on.
Questions about create_script_include
Create a new script include (requires SCRIPTING_ENABLED=true). It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for create_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 Server. Nothing to install.
create_script_include is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_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 create_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.
create_script_include is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
Across the catalogue