New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

asc_post_app_store_version_release_request

⚠️ CUSTOMER-FACING: POST an appStoreVersionReleaseRequest to release a version that App Review has approved (state PENDING_DEVELOPER_RELEASE) to the public App Store immediately — the automated form of the manual

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-app-store-version-release-request.md

What asc_post_app_store_version_release_request does on Appstoreconnect Mcp

AI agents invoke asc_post_app_store_version_release_request 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_post_app_store_version_release_request is rated High

Triggers immediate public release of an app, irreversibly affecting all customers.

From the tool's definition release a version...to the public App Store immediately

Questions about asc_post_app_store_version_release_request

What does the asc_post_app_store_version_release_request tool do? +

⚠️ CUSTOMER-FACING: POST an appStoreVersionReleaseRequest to release a version that App Review has approved (state PENDING_DEVELOPER_RELEASE) to the public App Store immediately — the automated form of the manual. 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.

How do I enforce a policy on asc_post_app_store_version_release_request? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_post_app_store_version_release_request: 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.

What risk level is asc_post_app_store_version_release_request? +

asc_post_app_store_version_release_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit asc_post_app_store_version_release_request? +

Yes. Add a rate_limit block to the asc_post_app_store_version_release_request 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.

How do I block asc_post_app_store_version_release_request completely? +

Set action: deny in the PolicyLayer policy for asc_post_app_store_version_release_request. 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.

What MCP server provides asc_post_app_store_version_release_request? +

asc_post_app_store_version_release_request 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appstoreconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.