list_subscription_events
Subscription lifecycle events (starts, cancels, renewals) over a date range.
This record as markdown: /tools/com-zype-mcp-server/list-subscription-events.md
What list_subscription_events does on Zype Com
AI agents call list_subscription_events to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
offset | number | — | |
plan_id | string | — | |
group_by | array | — | |
interval | string | — | |
start_date_gte | string | — | Start date (YYYY-MM-DD) |
start_date_lte | string | — | End date (YYYY-MM-DD) |
Parameters from the server's own tool schema.
Why list_subscription_events is rated Low
Even though list_subscription_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_subscription_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_subscription_events, this is the rule to start with:
list_subscription_events 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 Zype Com, apply this rule, and every list_subscription_events call is checked against it from then on.
Questions about list_subscription_events
Subscription lifecycle events (starts, cancels, renewals) over a date range. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.
list_subscription_events accepts 7 parameters: limit, offset, plan_id, group_by, interval, start_date_gte, start_date_lte. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for list_subscription_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 Zype Com. Nothing to install.
list_subscription_events 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 list_subscription_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 list_subscription_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.
list_subscription_events is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
This server
Across the catalogue