snow_get_flow_execution_logs

Retrieve Flow Designer execution logs for monitoring flow runs, debugging failures, and analyzing performance

Server Serac serac-labs/serac
Category Read
Risk class Low
Parameters 00 required

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 — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why snow_get_flow_execution_logs needs a policy

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.

Questions about snow_get_flow_execution_logs

What does the snow_get_flow_execution_logs tool do? +

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.

How do I enforce a policy on snow_get_flow_execution_logs? +

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.

What risk level is snow_get_flow_execution_logs? +

snow_get_flow_execution_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit snow_get_flow_execution_logs? +

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.

How do I block snow_get_flow_execution_logs completely? +

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.

What MCP server provides snow_get_flow_execution_logs? +

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.

// THE FULL RECORD

snow_get_flow_execution_logs is one line of Serac's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.