create_scheduled_job
Create a new scheduled script execution job (requires WRITE_ENABLED=true)
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/create-scheduled-job.md
What create_scheduled_job does on NowAIKit — ServiceNow AI Toolkit
AI agents invoke create_scheduled_job to trigger actions in NowAIKit — ServiceNow AI Toolkit. 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_scheduled_job is rated High
While the act of creating the job is a Write operation, the primary risk is that it schedules arbitrary script execution on the ServiceNow platform. A misused tool could cause repeated execution of malicious or destructive scripts. The Execute category is more appropriate given the blast radius of scheduled script execution, which outweighs the Write aspect of job creation.
From the tool's definition 'Create a new scheduled script execution job' — this tool creates a job that will execute scripts on a schedule
Attacks that exploit this kind of access
The rule that runs create_scheduled_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NowAIKit — ServiceNow AI Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_scheduled_job, this is the rule to start with:
create_scheduled_job 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 NowAIKit — ServiceNow AI Toolkit, apply this rule, and every create_scheduled_job call is checked against it from then on.
Questions about create_scheduled_job
Create a new scheduled script execution job (requires WRITE_ENABLED=true). It is categorised as a Execute tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NowAIKit — ServiceNow AI Toolkit MCP server in PolicyLayer and add a rule for create_scheduled_job: 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 NowAIKit — ServiceNow AI Toolkit. Nothing to install.
create_scheduled_job 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_scheduled_job 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_scheduled_job. 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_scheduled_job is provided by the NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.
Across the catalogue