asc_post_app_custom_product_page_version
Create a new AppCustomProductPageVersion under a CPP. Required: appCustomProductPageId. Optional: deepLink (URL appended to the CPP click-through). No-attrs-block gotcha: when deepLink is omitted, the body sends NO attributes key at all (Apple rejects bare attrs:{} on this endpoint, same as v0.9 ...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-app-custom-product-page-version.md
What asc_post_app_custom_product_page_version does on Appstoreconnect Mcp
AI agents use asc_post_app_custom_product_page_version 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_custom_product_page_version is rated Medium
This tool creates new product page versions in App Store Connect, which is a write operation that modifies application metadata. While creations are reversible (new versions can be deleted or superseded), the tool affects published app listing content and could impact customer-facing product pages if misused by an agent.
From the tool's definition Tool name contains 'post' and description states 'Create a new AppCustomProductPageVersion' - a reversible creation operation that modifies App Store Connect data.
Attacks that exploit this kind of access
The rule that runs asc_post_app_custom_product_page_version 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_custom_product_page_version, this is the rule to start with:
asc_post_app_custom_product_page_version 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_custom_product_page_version call is checked against it from then on.
Questions about asc_post_app_custom_product_page_version
Create a new AppCustomProductPageVersion under a CPP. Required: appCustomProductPageId. Optional: deepLink (URL appended to the CPP click-through). No-attrs-block gotcha: when deepLink is omitted, the body sends NO attributes key at all (Apple rejects bare attrs:{} on this endpoint, same as v0.9 AppInfo PATCH). New versions land in PREPARE_FOR_SUBMISSION. 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_custom_product_page_version: 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_custom_product_page_version 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_custom_product_page_version 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_custom_product_page_version. 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_custom_product_page_version 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