list_task_instances
AI agents call list_task_instances 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 retrieves or lists task instances from Apache Airflow workflows. While the description is empty, the name and context strongly indicate a data query operation with no side effects. It serves monitoring purposes consistent with 'workflow execution monitoring' mentioned in the server description. There is no evidence of data modification, deletion, or code execution capability.
From the tool's definition Tool name 'list_task_instances' indicates a retrieval operation for querying task instance data. The MWAA server description confirms this server manages workflow monitoring and provides access to Airflow data.
Attacks that exploit this kind of access
list_task_instances. 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_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 MWAA MCP Server. Nothing to install.
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 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 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.
list_task_instances 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 →