asc_sign_promotional_offer
Sign a promotional-offer redemption payload using the JWS v2 format (recommended for new code; introduced WWDC 2025, back-deployed to iOS 15). Use this when your iOS app uses StoreKit 2
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-sign-promotional-offer.md
What asc_sign_promotional_offer does on Appstoreconnect Mcp
AI agents invoke asc_sign_promotional_offer to trigger actions in Appstoreconnect Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why asc_sign_promotional_offer is rated High
Signing a promotional offer payload is an Execute action: it runs a cryptographic operation to produce a signed token. While it doesn't directly move money, the output (a signed promotional offer) can be redeemed by users to get discounted or free subscriptions, making misuse financially impactful.
From the tool's definition 'Sign a promotional-offer redemption payload using the JWS v2 format' — this triggers a cryptographic signing operation that generates a payload used for StoreKit promotional offers
Attacks that exploit this kind of access
The rule that runs asc_sign_promotional_offer 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_sign_promotional_offer, this is the rule to start with:
asc_sign_promotional_offer stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_sign_promotional_offer call is checked against it from then on.
Questions about asc_sign_promotional_offer
Sign a promotional-offer redemption payload using the JWS v2 format (recommended for new code; introduced WWDC 2025, back-deployed to iOS 15). Use this when your iOS app uses StoreKit 2. It is categorised as a Execute tool in the Appstoreconnect Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_sign_promotional_offer: 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_sign_promotional_offer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the asc_sign_promotional_offer 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_sign_promotional_offer. 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_sign_promotional_offer 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.
Across the catalogue