get_sys_log
Retrieve system log entries for debugging or auditing. Set app_scope=true to read the scoped-application log (syslog_app_scope), where scoped gs.info()/gs.log() output lands, instead of the global syslog.
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/get-sys-log.md
What get_sys_log does on NowAIKit — ServiceNow AI Toolkit
AI agents call get_sys_log 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 get_sys_log is rated Low
Tool retrieves log data without modification; medium severity due to potential exposure of sensitive system information in logs.
From the tool's definition Retrieve system log entries for debugging or auditing.
Attacks that exploit this kind of access
The rule that runs get_sys_log 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 get_sys_log, this is the rule to start with:
get_sys_log 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 get_sys_log call is checked against it from then on.
Questions about get_sys_log
Retrieve system log entries for debugging or auditing. Set app_scope=true to read the scoped-application log (syslog_app_scope), where scoped gs.info()/gs.log() output lands, instead of the global syslog. 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 get_sys_log: 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.
get_sys_log 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 get_sys_log 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 get_sys_log. 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.
get_sys_log 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