sync_integration

SERVERSequenzy Mcp SOURCESequenzy/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/sync-integration.md

WHAT IT DOES

What sync_integration does on Sequenzy Mcp

AI agents invoke sync_integration to trigger actions in Sequenzy Mcp. 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.

RISK

Why sync_integration is rated High

Triggers external operations with side effects on revenue data and user attributes across multiple systems.

From the tool's definition Queue a manual re-sync for an integration: customers and revenue for payment providers; user backfill; event-history import.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sync_integration safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_integration, this is the rule to start with:

sync_integration Rate-limited

sync_integration 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": {
    "sync_integration": {
      "limits": [
        {
          "counter": "sync_integration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every sync_integration call is checked against it from then on.

FAQ

Questions about sync_integration

What does the sync_integration tool do? +

Queue a manual re-sync for an integration: customers and revenue for a payment provider (Stripe, Polar, Paddle, Dodo, Creem, Chargebee, Whop), the user backfill for Supabase, or the event-history import for PostHog and Segment. Use this for Supabase before a campaign that depends on names or plan attributes - the live trigger only sends rows that change after it was installed, so existing users have no attributes until a backfill runs. The Supabase sync reads the project, schema, and table already configured for the integration and cannot be pointed at a different table; if none is configured yet it fails saying so. This is also the supported way to retry a failed PostHog or Segment history import: it restarts from the beginning using the stored credentials, and already-imported events dedupe, so a re-run cannot duplicate them. Returns immediately - poll get_integration to watch. It is categorised as a Execute tool in the Sequenzy Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sync_integration? +

Register the Sequenzy MCP server in PolicyLayer and add a rule for sync_integration: 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 Sequenzy Mcp. Nothing to install.

What risk level is sync_integration? +

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

Can I rate-limit sync_integration? +

Yes. Add a rate_limit block to the sync_integration 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 sync_integration completely? +

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

sync_integration is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sequenzy, and thousands of servers like it.

This server

All 222 Sequenzy tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →