asc_post_version_experiment
POST /v2/appStoreVersionExperiments — create an A/B test on the product page. ALL THREE attributes required: name, platform, trafficProportion (1–99% of page traffic, split across treatments). Created in PREPARE_FOR_SUBMISSION; it shows nothing publicly until submitted (V2 review submission flow,...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-version-experiment.md
What asc_post_version_experiment does on Appstoreconnect Mcp
AI agents use asc_post_version_experiment 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_version_experiment is rated Medium
This tool creates and configures A/B test experiments on App Store product pages, which is a write operation that modifies app configuration and marketing strategy. While the experiments don't become publicly visible until explicitly submitted and started, the tool irreversibly commits experimental configurations that affect user-facing product presentation and traffic allocation (1-99% splits).
From the tool's definition POST /v2/appStoreVersionExperiments — create an A/B test on the product page
Attacks that exploit this kind of access
The rule that runs asc_post_version_experiment 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_version_experiment, this is the rule to start with:
asc_post_version_experiment 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_version_experiment call is checked against it from then on.
Questions about asc_post_version_experiment
POST /v2/appStoreVersionExperiments — create an A/B test on the product page. ALL THREE attributes required: name, platform, trafficProportion (1–99% of page traffic, split across treatments). Created in PREPARE_FOR_SUBMISSION; it shows nothing publicly until submitted (V2 review submission flow, v0.11 tools) AND explicitly started (asc_patch_version_experiment started=true after APPROVED). Build flow: create → add treatments → add treatment localizations → attach variant screenshots via the v0.13 asset tools → submit → start. 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_version_experiment: 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_version_experiment 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_version_experiment 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_version_experiment. 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_version_experiment 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