asc_end_app_availability_pre_order
POST an EndAppAvailabilityPreOrder resource carrying the list of TerritoryAvailability IDs in which to end pre-order. Apple stops accepting pre-orders in those territories — the app either goes live (if past releaseDate) or back to
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-end-app-availability-pre-order.md
What asc_end_app_availability_pre_order does on Appstoreconnect Mcp
AI agents use asc_end_app_availability_pre_order 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_end_app_availability_pre_order is rated Medium
This tool POSTs a resource that ends pre-order availability in specified territories. While it is a significant action that affects app distribution and marketing strategy, it is a state change (ending pre-orders) rather than a deletion of data. The action could potentially be reversed by re-enabling pre-orders, placing it in Write rather than Destructive.
From the tool's definition POST an EndAppAvailabilityPreOrder resource carrying the list of TerritoryAvailability IDs in which to end pre-order. Apple stops accepting pre-orders in those territories
Attacks that exploit this kind of access
The rule that runs asc_end_app_availability_pre_order 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_end_app_availability_pre_order, this is the rule to start with:
asc_end_app_availability_pre_order 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_end_app_availability_pre_order call is checked against it from then on.
Questions about asc_end_app_availability_pre_order
POST an EndAppAvailabilityPreOrder resource carrying the list of TerritoryAvailability IDs in which to end pre-order. Apple stops accepting pre-orders in those territories — the app either goes live (if past releaseDate) or back to. 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_end_app_availability_pre_order: 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_end_app_availability_pre_order 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_end_app_availability_pre_order 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_end_app_availability_pre_order. 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_end_app_availability_pre_order 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