asc_patch_version_experiment
⚠️ started=true is CUSTOMER-FACING: PATCH /v2/appStoreVersionExperiments/{id} with started=true begins serving treatment pages to real App Store traffic (requires state APPROVED). Also mutates name and trafficProportion while still in PREPARE_FOR_SUBMISSION. Wire-key gotcha pinned by tests: the s...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-patch-version-experiment.md
What asc_patch_version_experiment does on Appstoreconnect Mcp
AI agents invoke asc_patch_version_experiment to trigger actions in Appstoreconnect Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why asc_patch_version_experiment is rated High
This tool triggers an external, customer-facing operation that affects live App Store traffic by starting an experiment — this is an Execute action with critical blast radius since misuse could expose unapproved or unintended content to real users at scale. It also mutates name and trafficProportion, adding Write behavior, but the live traffic impact makes Execute the dominant concern.
From the tool's definition started=true begins serving treatment pages to real App Store traffic (requires state APPROVED)... CUSTOMER-FACING
Attacks that exploit this kind of access
The rule that runs asc_patch_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_patch_version_experiment, this is the rule to start with:
asc_patch_version_experiment stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_patch_version_experiment call is checked against it from then on.
Questions about asc_patch_version_experiment
⚠️ started=true is CUSTOMER-FACING: PATCH /v2/appStoreVersionExperiments/{id} with started=true begins serving treatment pages to real App Store traffic (requires state APPROVED). Also mutates name and trafficProportion while still in PREPARE_FOR_SUBMISSION. Wire-key gotcha pinned by tests: the start flag is. It is categorised as a Execute tool in the Appstoreconnect Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_patch_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_patch_version_experiment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the asc_patch_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_patch_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_patch_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.
Across the catalogue