asc_post_app_preview

RAW step 1 of the three-step upload flow for previews. Reserves an AppPreview under a set with fileName + fileSize (+ optional previewFrameTimeCode + mimeType), and returns the resource with uploadOperations[] populated. Most callers should use the composite asc_upload_app_preview instead — this ...

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp
Medium RISK CLASS
Category Write
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-preview.md

What asc_post_app_preview does on Appstoreconnect Mcp

AI agents use asc_post_app_preview 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_app_preview is rated Medium

This tool creates/reserves a new AppPreview resource in App Store Connect, which is a reversible write operation. While it initiates an upload flow, the tool itself reserves/creates the preview object without executing the actual file transfer (uploadOperations are returned for subsequent steps).

From the tool's definition Tool reserves (creates) an AppPreview resource via upload flow that modifies App Store Connect data. Description states it 'Reserves an AppPreview' and 'returns the resource with uploadOperations[] populated', indicating creation/initialization of new data.

Questions about asc_post_app_preview

What does the asc_post_app_preview tool do? +

RAW step 1 of the three-step upload flow for previews. Reserves an AppPreview under a set with fileName + fileSize (+ optional previewFrameTimeCode + mimeType), and returns the resource with uploadOperations[] populated. Most callers should use the composite asc_upload_app_preview instead — this exists for manual control. 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.

How do I enforce a policy on asc_post_app_preview? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_post_app_preview: 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_preview? +

asc_post_app_preview is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit asc_post_app_preview? +

Yes. Add a rate_limit block to the asc_post_app_preview 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_preview completely? +

Set action: deny in the PolicyLayer policy for asc_post_app_preview. 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_preview? +

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