List recent executions of a flow with status (completed, error, running)
AI agents call list_flow_executions 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 historical execution records and their statuses from ServiceNow flows without creating, modifying, deleting, or executing any operations. It is a passive data retrieval mechanism with no blast radius if misused—worst case, an AI agent queries execution history, which poses minimal security risk.
From the tool's definition Tool name 'list_flow_executions' and description 'List recent executions of a flow with status' indicate retrieval/query of execution data with no modification or side effects. The verb 'list' is explicitly a Read operation.
Attacks that exploit this kind of access
List recent executions of a flow with status (completed, error, running). 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_flow_executions: 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_flow_executions 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_flow_executions 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_flow_executions. 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_flow_executions 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 →