List recent Virtual Agent conversations
AI agents call list_va_conversations to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing Virtual Agent conversation data without modifying, deleting, or executing any operations. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—an attacker could potentially view conversation history but cannot alter system state, trigger actions, or cause financial harm.
From the tool's definition Tool name 'list_va_conversations' with description 'List recent Virtual Agent conversations' indicates a retrieval operation. The verb 'list' and the absence of any modification, deletion, execution, or financial language confirm this is a read-only query.
Attacks that exploit this kind of access
List recent Virtual Agent conversations. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for list_va_conversations: 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.
list_va_conversations 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_va_conversations 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_va_conversations. 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_va_conversations 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.
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 →