AI agents use airbyte_create_destination to create or update resources in Airbyte — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Airbyte environment.
Creating a destination in Airbyte is a reversible write operation that adds a new data sink to the platform. While it modifies system configuration, it does not delete data or execute arbitrary code. However, severity is elevated to 'high' because misconfigured destinations could redirect data flows to unintended locations, potentially exposing sensitive data or disrupting pipeline operations.
From the tool's definition Tool name 'airbyte_create_destination' indicates creation of a destination resource in Airbyte. Server description confirms support for 'destinations' - systems that receive data from sources in ETL pipelines.
Attacks that exploit this kind of access
airbyte_create_destination. It is categorised as a Write tool in the Airbyte MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Airbyte MCP server in PolicyLayer and add a rule for airbyte_create_destination: 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_create_destination is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the airbyte_create_destination 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_create_destination. 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_create_destination 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 →