Create a new script include (requires SCRIPTING_ENABLED=true)
AI agents invoke create_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.
Script includes are reusable server-side JavaScript libraries in ServiceNow. Creating one introduces executable code into the platform that can be invoked by other scripts, business rules, or workflows. This is effectively arbitrary code execution with platform-wide blast radius. The SCRIPTING_ENABLED guard confirms the elevated risk.
From the tool's definition 'Create a new script include (requires SCRIPTING_ENABLED=true)' — creates executable server-side JavaScript code in ServiceNow
Attacks that exploit this kind of access
Create a new 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.
Register the ServiceNow- 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. 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 (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →