List task instances for a DAG run
AI agents call airflow_list_task_instances to retrieve information from MCP Server for Apache Airflow 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 metadata about task instances within a Airflow DAG run. It performs no mutations, deletions, executions, or financial operations. Even if misused by an AI agent, it can only expose information about workflow status and history, with minimal blast radius. The confidence is high given the clear read-only semantics of a 'list' operation.
From the tool's definition Tool name 'airflow_list_task_instances' and description 'List task instances for a DAG run' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List task instances for a DAG run. It is categorised as a Read tool in the MCP Server for Apache Airflow MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Apache Airflow MCP server in PolicyLayer and add a rule for airflow_list_task_instances: 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 MCP Server for Apache Airflow. Nothing to install.
airflow_list_task_instances 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 airflow_list_task_instances 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 airflow_list_task_instances. 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.
airflow_list_task_instances is provided by the MCP Server for Apache Airflow MCP server (tomnagengast/mcp-server-airflow). 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 →