AI agents call airbyte_list_connections to retrieve information from Airbyte without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries a list of Airbyte connections without modifying any data. No side effects are indicated. Listed among tools with get_* and similar patterns that are typical Read category operations (retrieving metadata about connections, destinations, sources, etc.). The absence of words like 'create', 'delete', 'update', 'execute', or 'cancel' confirms this is a simple retrieval/enumeration operation.
From the tool's definition Tool name 'airbyte_list_connections' and its position among sibling tools (get_*, list_*) that perform data retrieval operations. The 'list_' prefix is characteristic of read-only enumeration operations.
Attacks that exploit this kind of access
airbyte_list_connections. It is categorised as a Read tool in the Airbyte MCP Server, which means it retrieves data without modifying state.
Register the Airbyte MCP server in PolicyLayer and add a rule for airbyte_list_connections: 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_list_connections 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 airbyte_list_connections 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_list_connections. 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_list_connections 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 →