asc_post_alternative_distribution_package
POST /v1/alternativeDistributionPackages — start packaging an App Store Version for alternative distribution. Relationships-only body (appStoreVersion). Apple builds the signed package asynchronously; poll asc_list_alternative_distribution_package_versions until a version reaches COMPLETED.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-alternative-distribution-package.md
What asc_post_alternative_distribution_package does on Appstoreconnect Mcp
AI agents invoke asc_post_alternative_distribution_package 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_post_alternative_distribution_package is rated High
This tool triggers an external asynchronous build/packaging operation on Apple's servers. It's not a simple write of data—it initiates a pipeline that produces a signed distribution package. The closest category is Execute, as it triggers an external operation whose effects depend on arguments (which App Store Version is packaged for alternative distribution).
From the tool's definition start packaging an App Store Version for alternative distribution... Apple builds the signed package asynchronously
Attacks that exploit this kind of access
The rule that runs asc_post_alternative_distribution_package 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_alternative_distribution_package, this is the rule to start with:
asc_post_alternative_distribution_package 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_post_alternative_distribution_package call is checked against it from then on.
Questions about asc_post_alternative_distribution_package
POST /v1/alternativeDistributionPackages — start packaging an App Store Version for alternative distribution. Relationships-only body (appStoreVersion). Apple builds the signed package asynchronously; poll asc_list_alternative_distribution_package_versions until a version reaches COMPLETED. 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_post_alternative_distribution_package: 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_alternative_distribution_package 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_post_alternative_distribution_package 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_alternative_distribution_package. 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_alternative_distribution_package 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