list_dag_runs
AI agents call list_dag_runs to retrieve information from MWAA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data about DAG (Directed Acyclic Graph) runs—workflow execution history and status—with no side effects. Although the description is empty, the naming convention and position among sibling tools (which include monitoring/retrieval operations like 'get_dag', 'get_dag_run', 'get_dag_run_heatmap') strongly indicate it performs read-only list/query operations on MWAA workflow metadata.
From the tool's definition Tool name 'list_dag_runs' indicates retrieval of DAG run records; absence of deletion, modification, execution, or financial keywords; consistent with 'get_dag_run' sibling tool which queries workflow execution state.
Attacks that exploit this kind of access
list_dag_runs. It is categorised as a Read tool in the MWAA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MWAA MCP Server MCP server in PolicyLayer and add a rule for list_dag_runs: 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 MWAA MCP Server. Nothing to install.
list_dag_runs 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_dag_runs 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_dag_runs. 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_dag_runs is provided by the MWAA MCP Server MCP server (paschmaria/mwaa-mcp-server). 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 →