Execute JavaScript on a ServiceNow instance using Scripts - Background
AI agents invoke execute_script to trigger actions in Now Sdk Ext. 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.
This tool permits execution of JavaScript code on a ServiceNow instance, which is a classic Execute action. The blast radius is critical because JavaScript execution in a ServiceNow backend environment can: (1) access and modify any data the service account has permissions for, (2) trigger workflows and integrations, (3) interact with external systems, and (4) cause widespread system changes depending on the script…
From the tool's definition Tool name 'execute_script' combined with description 'Execute JavaScript on a ServiceNow instance using Scripts - Background' explicitly indicates arbitrary code execution capability.
Documented attack patterns abuse exactly the kind of access execute_script gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_script:
{
"version": "1",
"default": "deny",
"tools": {
"execute_script": {
"limits": [
{
"counter": "execute_script_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} execute_script 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.
Free to start. No card required.
Execute JavaScript on a ServiceNow instance using Scripts - Background. It is categorised as a Execute tool in the Now Sdk Ext MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for execute_script: 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 Now Sdk Ext. Nothing to install.
execute_script 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 execute_script 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 execute_script. 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.
execute_script is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Now Sdk Ext, 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.
86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.