asc_post_alternative_distribution_key
POST /v1/alternativeDistributionKeys — register the PUBLIC key (PEM string) used to verify your signed alternative-distribution artifacts. Optionally scope to one app via appId. The private key stays with you — never paste it anywhere; this tool takes the PUBLIC half only.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-alternative-distribution-key.md
What asc_post_alternative_distribution_key does on Appstoreconnect Mcp
AI agents use asc_post_alternative_distribution_key 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_alternative_distribution_key is rated Medium
This tool creates/registers a new alternative distribution key in App Store Connect. The POST operation with 'register' language indicates it writes/creates a new security artifact (the public key) in the system. While it explicitly handles only the PUBLIC key (reducing risk vs. private key exposure), registration of cryptographic keys is a write operation that establishes trust for alternative distribution channels.
From the tool's definition POST /v1/alternativeDistributionKeys — register the PUBLIC key (PEM string)
Attacks that exploit this kind of access
The rule that runs asc_post_alternative_distribution_key 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_key, this is the rule to start with:
asc_post_alternative_distribution_key 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_alternative_distribution_key call is checked against it from then on.
Questions about asc_post_alternative_distribution_key
POST /v1/alternativeDistributionKeys — register the PUBLIC key (PEM string) used to verify your signed alternative-distribution artifacts. Optionally scope to one app via appId. The private key stays with you — never paste it anywhere; this tool takes the PUBLIC half only. 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_alternative_distribution_key: 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_key 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_alternative_distribution_key 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_key. 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_key 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