trigger_scheduled_job

Immediately execute a scheduled job on-demand (requires WRITE_ENABLED=true)

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/servicenow-mcp-server/trigger-scheduled-job.md

What trigger_scheduled_job does on ServiceNow MCP Server

AI agents invoke trigger_scheduled_job 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 trigger_scheduled_job is rated High

This tool executes a scheduled job outside its normal schedule, which constitutes an Execute-category action per the rules. The 'immediate' trigger of a job whose side effects are dependent on its specific configuration and payload represents a code/operation execution risk.

From the tool's definition Immediately execute a scheduled job on-demand; tool enables triggering external operations whose effects depend on job configuration and arguments

Questions about trigger_scheduled_job

What does the trigger_scheduled_job tool do? +

Immediately execute a scheduled job on-demand (requires WRITE_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.

How do I enforce a policy on trigger_scheduled_job? +

Register the ServiceNow MCP Server 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 ServiceNow MCP Server. Nothing to install.

What risk level is trigger_scheduled_job? +

trigger_scheduled_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_scheduled_job? +

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.

How do I block trigger_scheduled_job completely? +

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.

What MCP server provides trigger_scheduled_job? +

trigger_scheduled_job 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ServiceNow MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.