AI agents call get_flow_run_logs to retrieve information from Prefect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical log data from completed or running flow executions. It performs no modifications, deletions, or side effects—it only queries and returns existing log information. The 'get_' prefix and cohort with other retrieval tools confirm read-only semantics. No blast radius for misuse; logs are informational.
From the tool's definition Tool name 'get_flow_run_logs' and context within a Prefect workflow monitoring server indicate this retrieves log data.
Documented attack patterns abuse exactly the kind of access get_flow_run_logs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prefect, and nothing reaches the server without passing your rules. This is the rule we recommend for get_flow_run_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_flow_run_logs": {}
}
}get_flow_run_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_flow_run_logs. It is categorised as a Read tool in the Prefect MCP Server, which means it retrieves data without modifying state.
Register the Prefect MCP server in PolicyLayer and add a rule for get_flow_run_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 Prefect. Nothing to install.
get_flow_run_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 get_flow_run_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 get_flow_run_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.
get_flow_run_logs is provided by the Prefect MCP server (prefecthq/prefect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Prefect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Prefect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.