asc_list_version_experiments
GET /v1/apps/{id}/appStoreVersionExperimentsV2 (note: a /v1 path listing the V2, app-attached experiments — the modern surface). Each row shows name, state (9-state lifecycle), platform, traffic %, review-required flag, and start/end dates. Filter client-side by state from the digest.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-version-experiments.md
What asc_list_version_experiments does on Appstoreconnect Mcp
AI agents call asc_list_version_experiments to retrieve information from Appstoreconnect Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why asc_list_version_experiments is rated Low
This tool queries and lists app store version experiments without side effects. It retrieves read-only data about experiment configurations and states. The 'list' operation and GET method confirm it is a Read category tool. Severity is low because the data exposed (experiment names, states, platform info, traffic percentages, dates) is informational and does not directly enable harm if misused by an AI agent.
From the tool's definition GET /v1/apps/{id}/appStoreVersionExperimentsV2 — retrieves a list of experiments with metadata (name, state, platform, traffic %, dates); no modification or deletion occurs.
Attacks that exploit this kind of access
The rule that runs asc_list_version_experiments 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_list_version_experiments, this is the rule to start with:
asc_list_version_experiments is read-only, so it stays allowed. 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_list_version_experiments call is checked against it from then on.
Questions about asc_list_version_experiments
GET /v1/apps/{id}/appStoreVersionExperimentsV2 (note: a /v1 path listing the V2, app-attached experiments — the modern surface). Each row shows name, state (9-state lifecycle), platform, traffic %, review-required flag, and start/end dates. Filter client-side by state from the digest. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_list_version_experiments: 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_list_version_experiments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the asc_list_version_experiments 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_list_version_experiments. 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_list_version_experiments 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