import_subscriber_events
Record a bounded batch of events for many subscribers in one call, built for data pipeline and warehouse syncs. Each event carries its own email or externalId and a required source-owned eventId; externalId-only rows must identify an existing contact because email is required for creation. Contac...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/import-subscriber-events.md
What import_subscriber_events does on Sequenzy Mcp
AI agents use import_subscriber_events to create or update resources in Sequenzy Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sequenzy Mcp environment.
Why import_subscriber_events is rated Medium
Imports event data and creates contacts with potential email side effects; reversible operations without permanent deletion.
From the tool's definition import_subscriber_events records batch events for subscribers, adds contacts, sends emails
Attacks that exploit this kind of access
The rule that runs import_subscriber_events 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 import_subscriber_events, this is the rule to start with:
import_subscriber_events stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every import_subscriber_events call is checked against it from then on.
Questions about import_subscriber_events
Record a bounded batch of events for many subscribers in one call, built for data pipeline and warehouse syncs. Each event carries its own email or externalId and a required source-owned eventId; externalId-only rows must identify an existing contact because email is required for creation. Contacts whose events are all more than an hour old are imported silently as history (including no double-opt-in email); any recent event makes that contact. It is categorised as a Write tool in the Sequenzy Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sequenzy MCP server in PolicyLayer and add a rule for import_subscriber_events: 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.
import_subscriber_events 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 import_subscriber_events 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 import_subscriber_events. 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.
import_subscriber_events 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.
More on Sequenzy, and thousands of servers like it.
This server
Across the catalogue