get_subscriber
Get the full subscriber profile, including tags, notes, list memberships, sequence enrollments, email stats, and recent activity. For commerce customers, customAttributes include nightly predictive analytics: predictedLtv (next-12-month spend), churnRisk (percent), expectedNextOrderAt, avgDaysBet...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/get-subscriber.md
What get_subscriber does on Sequenzy Mcp
AI agents call get_subscriber to retrieve information from Sequenzy Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_subscriber is rated Low
This is fundamentally a retrieval/query operation that returns subscriber data without modifying or deleting anything. It falls cleanly into the Read category. Severity is medium (not low) because subscriber profiles can contain sensitive personal data, behavioral patterns, and commerce predictions that could be misused if an AI agent over-queries or leaks the information; however, the tool itself does not modify,…
From the tool's definition Tool description states it 'Get[s] the full subscriber profile' and retrieves 'tags, notes, list memberships, sequence enrollments, email stats, and recent activity' — all read operations with no data modification.
Attacks that exploit this kind of access
The rule that runs get_subscriber 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 get_subscriber, this is the rule to start with:
get_subscriber is read-only, so it stays allowed. 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 get_subscriber call is checked against it from then on.
Questions about get_subscriber
Get the full subscriber profile, including tags, notes, list memberships, sequence enrollments, email stats, and recent activity. For commerce customers, customAttributes include nightly predictive analytics: predictedLtv (next-12-month spend), churnRisk (percent), expectedNextOrderAt, avgDaysBetweenOrders, and predictionConfidence. It is categorised as a Read tool in the Sequenzy Mcp MCP Server, which means it retrieves data without modifying state.
Register the Sequenzy MCP server in PolicyLayer and add a rule for get_subscriber: 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.
get_subscriber is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_subscriber 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 get_subscriber. 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.
get_subscriber 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