snow_get_flow_execution_logs
Retrieve Flow Designer execution logs for monitoring flow runs, debugging failures, and analyzing performance
This record as markdown: /tools/serac/snow-get-flow-execution-logs.md
What snow_get_flow_execution_logs does on Serac
AI agents call snow_get_flow_execution_logs to retrieve information from Serac without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why snow_get_flow_execution_logs is rated Low
This tool retrieves and queries execution logs from ServiceNow Flow Designer. It has no side effects—it only reads data for monitoring, debugging, and analysis purposes. No data is created, modified, deleted, or destroyed. No code is executed and no external operations are triggered. This is a straightforward Read category tool.
From the tool's definition Tool name contains 'get' and description states 'Retrieve Flow Designer execution logs for monitoring flow runs, debugging failures, and analyzing performance' — all read-only operations that query existing log data without modifying or deleting it.
Attacks that exploit this kind of access
The rule that runs snow_get_flow_execution_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_get_flow_execution_logs, this is the rule to start with:
snow_get_flow_execution_logs 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 Serac, apply this rule, and every snow_get_flow_execution_logs call is checked against it from then on.
Questions about snow_get_flow_execution_logs
Retrieve Flow Designer execution logs for monitoring flow runs, debugging failures, and analyzing performance. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.
Register the Serac MCP server in PolicyLayer and add a rule for snow_get_flow_execution_logs: 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 Serac. Nothing to install.
snow_get_flow_execution_logs 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 snow_get_flow_execution_logs 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 snow_get_flow_execution_logs. 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.
snow_get_flow_execution_logs is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue