list_recent_failures
AI agents call list_recent_failures 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 information about recent workflow failures in MWAA/Airflow environments. While the description is empty and provides no explicit confirmation, the naming pattern aligns with monitoring and observability functions (similar to sibling tools like 'get_dag_run' and 'get_dag_run_heatmap'). There is no evidence of side effects, data modification, code execution, or financial impact.
From the tool's definition Tool name 'list_recent_failures' indicates a query/retrieval operation that lists historical failure data without modifying state. The absence of verbs like 'delete', 'create', 'update', 'execute', or 'trigger' suggests read-only functionality.
Attacks that exploit this kind of access
list_recent_failures. 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_recent_failures: 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_recent_failures 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_recent_failures 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_recent_failures. 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_recent_failures 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 →