list_job_run_history
List recent run history for scheduled jobs (success/failure log)
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/list-job-run-history.md
What list_job_run_history does on NowAIKit — ServiceNow AI Toolkit
AI agents call list_job_run_history to retrieve information from NowAIKit — ServiceNow AI Toolkit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_job_run_history is rated Low
This tool queries and retrieves historical execution logs for scheduled jobs, presenting success/failure information. It has no capacity to modify, delete, or execute operations—only to read and display existing log records. The blast radius of misuse is minimal, limited to information disclosure of job execution status, which is typically low-sensitivity operational data in ServiceNow.
From the tool's definition Tool name 'list_job_run_history' combined with description 'List recent run history for scheduled jobs (success/failure log)' indicates retrieval of historical log data without modification capability.
Attacks that exploit this kind of access
The rule that runs list_job_run_history 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 list_job_run_history, this is the rule to start with:
list_job_run_history is read-only, so it stays allowed. 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 list_job_run_history call is checked against it from then on.
Questions about list_job_run_history
List recent run history for scheduled jobs (success/failure log). It is categorised as a Read tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it retrieves data without modifying state.
Register the NowAIKit — ServiceNow AI Toolkit MCP server in PolicyLayer and add a rule for list_job_run_history: 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.
list_job_run_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_job_run_history 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 list_job_run_history. 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.
list_job_run_history 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.
This server
Across the catalogue