List journal entries (work notes, comments) for a record
AI agents call journal_list to retrieve information from ServiceNow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical journal entries (work notes and comments) associated with a ServiceNow record. The verb 'list' and the read-only nature of accessing existing journal entries classify this as a Read operation. Severity is low because reading audit/comment trails does not cause system changes, though access control should still protect sensitive information based on organizational policies.
From the tool's definition Tool name 'journal_list' and description 'List journal entries (work notes, comments) for a record' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List journal entries (work notes, comments) for a record. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for journal_list: 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.
journal_list 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 journal_list 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 journal_list. 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.
journal_list is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →