asc_post_app_availability_v2
Create a new AppAvailabilityV2 for an app — Apple atomically swaps over to it. There is NO PATCH for this resource; you replace the whole availability by POSTing a new record. Required: appId + availableInNewTerritories + the FULL list of TerritoryAvailability IDs the app should be sold in (Apple...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-app-availability-v2.md
What asc_post_app_availability_v2 does on Appstoreconnect Mcp
AI agents use asc_post_app_availability_v2 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_availability_v2 is rated Medium
This tool creates or modifies availability configurations for an app across territories. While the operation affects business-critical app distribution and sales availability globally, it is reversible—a new availability configuration can be posted to replace the current one. The action does not delete data, move money, or execute arbitrary code; it modifies app metadata in a controlled manner.
From the tool's definition Tool description explicitly states 'Create a new AppAvailabilityV2' and 'you replace the whole availability by POSTing a new record.' The POST operation and creation semantics clearly indicate data modification.
Attacks that exploit this kind of access
The rule that runs asc_post_app_availability_v2 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_availability_v2, this is the rule to start with:
asc_post_app_availability_v2 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_availability_v2 call is checked against it from then on.
Questions about asc_post_app_availability_v2
Create a new AppAvailabilityV2 for an app — Apple atomically swaps over to it. There is NO PATCH for this resource; you replace the whole availability by POSTing a new record. Required: appId + availableInNewTerritories + the FULL list of TerritoryAvailability IDs the app should be sold in (Apple-opaque base64 composites from asc_list_territory_availabilities; missing ones get removed). Wire-key gotcha: Swift. 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_availability_v2: 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_availability_v2 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_availability_v2 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_availability_v2. 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_availability_v2 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