trigger_scheduled_job · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What trigger_scheduled_job does on ServiceNow-MCP

AI agents invoke trigger_scheduled_job 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.

WHY IT NEEDS A POLICY

Why trigger_scheduled_job needs a policy

This tool triggers execution of a pre-defined scheduled job in ServiceNow. While the job itself is pre-existing (limiting some risk), the ability to execute it on-demand rather than on its scheduled cadence can have unpredictable side effects depending on the job's logic (data operations, integrations, notifications, remediations).

From the tool's definition "Immediately execute a scheduled job on-demand" — the tool runs a scheduled job outside its normal schedule based on caller discretion, which is a form of code execution or external operation triggering.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_scheduled_job Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_scheduled_job": {
      "limits": [
        {
          "counter": "trigger_scheduled_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow-MCP, so you can run agents against it safely.

FAQ

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 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 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. 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 (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.