bulk_create_redemption_codes
Generate many redemption codes at once via /redemption_codes/bulk_create.
This record as markdown: /tools/com-zype-mcp-server/bulk-create-redemption-codes.md
What bulk_create_redemption_codes does on Zype Com
AI agents use bulk_create_redemption_codes to create or update resources in Zype Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zype Com environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | — | Your own code; omit to auto-generate |
plan_id | string | — | |
quantity | number | — | How many to generate |
video_id | string | — | |
playlist_id | string | — | |
expiration_date | string | Yes | Expiration date e.g. 2027-01-15 (required) |
Parameters from the server's own tool schema.
Why bulk_create_redemption_codes is rated Medium
An AI agent can call bulk_create_redemption_codes faster than any human can review: one bad instruction and it creates or modifies resources in Zype Com by the hundred, each call as confident as the last.
Risk signalsAccepts freeform code/query input (code) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_create_redemption_codes 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 bulk_create_redemption_codes, this is the rule to start with:
bulk_create_redemption_codes 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 Zype Com, apply this rule, and every bulk_create_redemption_codes call is checked against it from then on.
Questions about bulk_create_redemption_codes
Generate many redemption codes at once via /redemption_codes/bulk_create. It is categorised as a Write tool in the Zype Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
bulk_create_redemption_codes accepts 6 parameters: code, plan_id, quantity, video_id, playlist_id, expiration_date. Required: expiration_date. 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 bulk_create_redemption_codes: 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.
bulk_create_redemption_codes 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 bulk_create_redemption_codes 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 bulk_create_redemption_codes. 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.
bulk_create_redemption_codes 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