New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERSequenzy Mcp SOURCESequenzy/mcp
Medium RISK CLASS
Category Write
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/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

Questions about import_subscriber_events

What does the import_subscriber_events tool do? +

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.

How do I enforce a policy on import_subscriber_events? +

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.

What risk level is import_subscriber_events? +

import_subscriber_events is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_subscriber_events? +

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.

How do I block import_subscriber_events completely? +

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.

What MCP server provides import_subscriber_events? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sequenzy's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.