trigger_scheduled_job
Immediately execute a scheduled job on-demand (requires WRITE_ENABLED=true)
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/trigger-scheduled-job.md
What trigger_scheduled_job does on NowAIKit — ServiceNow AI Toolkit
AI agents invoke trigger_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 trigger_scheduled_job is rated High
This tool runs scheduled jobs immediately, which are typically background processes that perform significant operations in ServiceNow (e.g., data imports, cleanup tasks, integrations, reports). While the tool itself doesn't directly delete or move money, scheduled jobs can perform destructive or financial operations, making the execution capability high-risk.
From the tool's definition Tool description states 'Immediately execute a scheduled job on-demand', indicating it triggers external operations whose effects depend on the job configuration. The requirement for WRITE_ENABLED=true suggests administrative controls around execution.
Attacks that exploit this kind of access
The rule that runs trigger_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 trigger_scheduled_job, this is the rule to start with:
trigger_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 trigger_scheduled_job call is checked against it from then on.
Questions about trigger_scheduled_job
Immediately execute a scheduled job on-demand (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 trigger_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.
trigger_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 trigger_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 trigger_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.
trigger_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