asc_list_app_store_version_localizations
List App Store version localizations under one version. Each row carries locale + whatsNew length/preview + description length + keywords + promotionalText. Use to see which locales already have copy before adding/patching more. THIS IS THE LLM-WIN ENTRY POINT: list, pick a source locale, transla...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-app-store-version-localizations.md
What asc_list_app_store_version_localizations does on Appstoreconnect Mcp
AI agents call asc_list_app_store_version_localizations 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_app_store_version_localizations is rated Low
The tool retrieves and displays metadata about App Store version localizations (locale, description length, keywords, promotional text). It performs no mutations, deletions, or external operations—purely informational retrieval to inspect existing localization data. The mention of 'LLM-WIN ENTRY POINT' confirms it is a read-only starting point for workflows, not the mutation step itself.
From the tool's definition Tool name contains 'list' and description states 'List App Store version localizations' and 'Use to see which locales already have copy before adding/patching more.' This is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs asc_list_app_store_version_localizations 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_app_store_version_localizations, this is the rule to start with:
asc_list_app_store_version_localizations 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_app_store_version_localizations call is checked against it from then on.
Questions about asc_list_app_store_version_localizations
List App Store version localizations under one version. Each row carries locale + whatsNew length/preview + description length + keywords + promotionalText. Use to see which locales already have copy before adding/patching more. THIS IS THE LLM-WIN ENTRY POINT: list, pick a source locale, translate into target locales, patch each. 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_app_store_version_localizations: 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_app_store_version_localizations 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_app_store_version_localizations 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_app_store_version_localizations. 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_app_store_version_localizations 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