asc_post_app_store_version_phased_release
Create a new AppStoreVersionPhasedRelease attached to an AppStoreVersion. Required: appStoreVersionId. Optional: phasedReleaseState — pass
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-app-store-version-phased-release.md
What asc_post_app_store_version_phased_release does on Appstoreconnect Mcp
AI agents use asc_post_app_store_version_phased_release 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_app_store_version_phased_release is rated Medium
This tool creates a new phased release configuration for an app version, which modifies deployment settings in App Store Connect. While reversible (configurations can be updated or deleted), it affects live app distribution to end users and can impact user experience at scale. The blast radius is significant—misconfiguration could roll out problematic app versions to large user populations unintentionally.
From the tool's definition Creates a new AppStoreVersionPhasedRelease attached to an AppStoreVersion; the verb 'Create' and 'post' operation indicate data creation/modification.
Attacks that exploit this kind of access
The rule that runs asc_post_app_store_version_phased_release 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_app_store_version_phased_release, this is the rule to start with:
asc_post_app_store_version_phased_release 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_app_store_version_phased_release call is checked against it from then on.
Questions about asc_post_app_store_version_phased_release
Create a new AppStoreVersionPhasedRelease attached to an AppStoreVersion. Required: appStoreVersionId. Optional: phasedReleaseState — pass. 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_app_store_version_phased_release: 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_app_store_version_phased_release 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_app_store_version_phased_release 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_app_store_version_phased_release. 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_app_store_version_phased_release 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