airbyte_trigger_sync · Airbyte MCP: Risk & Policy

WHAT IT DOES

What airbyte_trigger_sync does on Airbyte

AI agents invoke airbyte_trigger_sync to trigger actions in Airbyte. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why airbyte_trigger_sync needs a policy

Triggering a sync is an Execute-class action: it runs an external operation (data synchronization job) whose real-world effects depend on arguments and configuration. While not destructive (syncs are typically reversible), it performs work that affects data pipelines and systems.

From the tool's definition Tool name 'airbyte_trigger_sync' indicates triggering a synchronization job. Airbyte is a data integration platform, and triggering a sync initiates data movement operations whose effects depend on the connection configuration (source, destination, sync mode).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

airbyte_trigger_sync Rate-limited

airbyte_trigger_sync stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "airbyte_trigger_sync": {
      "limits": [
        {
          "counter": "airbyte_trigger_sync_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Airbyte, so you can run agents against it safely.

FAQ

Questions about airbyte_trigger_sync

What does the airbyte_trigger_sync tool do? +

airbyte_trigger_sync. It is categorised as a Execute tool in the Airbyte MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on airbyte_trigger_sync? +

Register the Airbyte MCP server in PolicyLayer and add a rule for airbyte_trigger_sync: 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.

What risk level is airbyte_trigger_sync? +

airbyte_trigger_sync is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit airbyte_trigger_sync? +

Yes. Add a rate_limit block to the airbyte_trigger_sync 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.

How do I block airbyte_trigger_sync completely? +

Set action: deny in the PolicyLayer policy for airbyte_trigger_sync. 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.

What MCP server provides airbyte_trigger_sync? +

airbyte_trigger_sync 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.