List audit history for a record
AI agents call audit_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 audit information about records, which is a non-destructive query operation. There are no side effects, data modifications, or irreversible changes. The blast radius of misuse is minimal—an attacker could view audit history they shouldn't see, but cannot alter records, execute commands, or cause financial harm. This is a standard Read category operation.
From the tool's definition Tool name 'audit_list' and description 'List audit history for a record' indicate retrieval of audit logs/history data without modification or deletion. The verb 'list' is a classic read operation.
Attacks that exploit this kind of access
List audit history 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 audit_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.
audit_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 audit_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 audit_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.
audit_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 →