create_subscriber_import
Queue one CRM-grade subscriber import with up to 5,000 full contact records. Supports names, external IDs, phones, statuses, tags, lists, and custom attributes. Prefer this over repeated add_subscriber calls. Returns an import ID for get_subscriber_import. Use optInMode=
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/create-subscriber-import.md
What create_subscriber_import does on Sequenzy Mcp
AI agents use create_subscriber_import 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 create_subscriber_import is rated Medium
This tool creates (writes) subscriber records in bulk—up to 5,000 contacts at once—which is reversible through standard delete/archive operations but has significant blast radius if misused (mass import of spam contacts, manipulation of subscriber lists, unauthorized contact addition). It does not execute arbitrary code, delete data irreversibly, or move money, so Write with high severity is appropriate.
From the tool's definition Tool description states 'Queue one CRM-grade subscriber import with up to 5,000 full contact records' and 'Supports names, external IDs, phones, statuses, tags, lists, and custom attributes.' The verb 'import' combined with creating up to 5,000 contact…
Attacks that exploit this kind of access
The rule that runs create_subscriber_import 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 create_subscriber_import, this is the rule to start with:
create_subscriber_import 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 create_subscriber_import call is checked against it from then on.
Questions about create_subscriber_import
Queue one CRM-grade subscriber import with up to 5,000 full contact records. Supports names, external IDs, phones, statuses, tags, lists, and custom attributes. Prefer this over repeated add_subscriber calls. Returns an import ID for get_subscriber_import. Use optInMode=. 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 create_subscriber_import: 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.
create_subscriber_import 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 create_subscriber_import 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 create_subscriber_import. 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.
create_subscriber_import 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