asc_post_subscription_offer_code_one_time_use_codes
Create a batch of unique single-redemption codes against an existing offer-code campaign. Apple generates the code strings server-side — retrieve them with asc_export_subscription_offer_code_one_time_use_values.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-subscription-offer-code-one-time-use-codes.md
What asc_post_subscription_offer_code_one_time_use_codes does on Appstoreconnect Mcp
AI agents use asc_post_subscription_offer_code_one_time_use_codes to create or update resources in Appstoreconnect Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appstoreconnect Mcp environment.
Why asc_post_subscription_offer_code_one_time_use_codes is rated Medium
This tool creates subscription offer codes that have monetary value in the App Store ecosystem. While not directly moving money (which would be Financial), it creates promotional instruments that reduce revenue and are bound to subscription campaigns.
From the tool's definition Tool description states 'Create a batch of unique single-redemption codes' — the word 'Create' indicates data creation.
Attacks that exploit this kind of access
The rule that runs asc_post_subscription_offer_code_one_time_use_codes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appstoreconnect Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For asc_post_subscription_offer_code_one_time_use_codes, this is the rule to start with:
asc_post_subscription_offer_code_one_time_use_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 Appstoreconnect Mcp, apply this rule, and every asc_post_subscription_offer_code_one_time_use_codes call is checked against it from then on.
Questions about asc_post_subscription_offer_code_one_time_use_codes
Create a batch of unique single-redemption codes against an existing offer-code campaign. Apple generates the code strings server-side — retrieve them with asc_export_subscription_offer_code_one_time_use_values. It is categorised as a Write tool in the Appstoreconnect Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_post_subscription_offer_code_one_time_use_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 Appstoreconnect Mcp. Nothing to install.
asc_post_subscription_offer_code_one_time_use_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 asc_post_subscription_offer_code_one_time_use_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 asc_post_subscription_offer_code_one_time_use_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.
asc_post_subscription_offer_code_one_time_use_codes is provided by the Appstoreconnect MCP server (@akoskomuves/appstoreconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appstoreconnect, and thousands of servers like it.
This server
Across the catalogue