airbyte_trigger_clear
AI agents call airbyte_trigger_clear to permanently remove resources in Airbyte — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
In Airbyte, a 'clear' operation resets a connection by deleting all synced data from the destination and re-syncing from scratch. This is effectively irreversible data deletion. The description is empty, so confidence is reduced, but the name strongly implies a destructive action. Severity is high due to potential data loss at scale.
From the tool's definition Tool name: airbyte_trigger_clear — 'clear' in Airbyte terminology refers to clearing (purging) synced data from a destination, which is an irreversible destructive operation.
Attacks that exploit this kind of access
airbyte_trigger_clear. It is categorised as a Destructive tool in the Airbyte MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Airbyte MCP server in PolicyLayer and add a rule for airbyte_trigger_clear: 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 Airbyte. Nothing to install.
airbyte_trigger_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the airbyte_trigger_clear 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 airbyte_trigger_clear. 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.
airbyte_trigger_clear is provided by the Airbyte MCP server (trustxai/airbyte-mcp). 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 →