AI agents call airbyte_get_source_definition 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 source connector definitions from Airbyte, which are read-only metadata about available source connectors. No data is created, modified, deleted, or executed. The blast radius is minimal—an AI agent accessing source definitions poses no risk of data loss, configuration changes, or resource misuse.
From the tool's definition Tool name 'airbyte_get_source_definition' with prefix 'get_' indicates a retrieval operation. The verb 'get' combined with 'definition' (a metadata/configuration artifact) suggests querying source connector definitions without modification.
Attacks that exploit this kind of access
airbyte_get_source_definition. 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_get_source_definition: 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_get_source_definition 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_get_source_definition 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_get_source_definition. 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_get_source_definition 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 →