asc_post_beta_build_localization
Create a BetaBuildLocalization for ONE build + ONE locale. whatsNew is optional at create time (you can leave it blank and patch later). The (build, locale) pair must be unique — Apple rejects a duplicate. Locale is immutable post-create; to change locale, delete this resource and re-create.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-beta-build-localization.md
What asc_post_beta_build_localization does on Appstoreconnect Mcp
AI agents use asc_post_beta_build_localization 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_beta_build_localization is rated Medium
This tool creates new data (a BetaBuildLocalization) in the App Store Connect system, making it a Write operation. It is reversible (the sibling tools show delete operations exist for similar resources), so it does not qualify as Destructive.
From the tool's definition Tool performs 'Create a BetaBuildLocalization' action, which explicitly creates a new resource in App Store Connect. The description states it creates a resource for a specific build and locale pair, with optional fields that can be patched later.
Attacks that exploit this kind of access
The rule that runs asc_post_beta_build_localization 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_beta_build_localization, this is the rule to start with:
asc_post_beta_build_localization 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_beta_build_localization call is checked against it from then on.
Questions about asc_post_beta_build_localization
Create a BetaBuildLocalization for ONE build + ONE locale. whatsNew is optional at create time (you can leave it blank and patch later). The (build, locale) pair must be unique — Apple rejects a duplicate. Locale is immutable post-create; to change locale, delete this resource and re-create. 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_beta_build_localization: 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_beta_build_localization 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_beta_build_localization 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_beta_build_localization. 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_beta_build_localization 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