asc_patch_app_preview
RAW step 3 of the three-step upload flow + the only way to tweak previewFrameTimeCode on an existing preview. PATCH with sourceFileChecksum + uploaded=true to commit a reservation, or with previewFrameTimeCode alone to change the poster frame without re-uploading the video. Wire-key gotcha: Swift
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-patch-app-preview.md
What asc_patch_app_preview does on Appstoreconnect Mcp
AI agents use asc_patch_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_patch_app_preview is rated Medium
This tool modifies preview metadata and completes upload workflows for app previews in App Store Connect. Changes are reversible (poster frames and upload status can be re-patched), so it is Write rather than Destructive. The scope is limited to preview assets within a specific app, reducing blast radius to medium severity.
From the tool's definition PATCH operation that modifies existing preview data (previewFrameTimeCode, uploaded status). Description states 'tweak previewFrameTimeCode on an existing preview' and 'commit a reservation', indicating reversible data modification rather than irreversible…
Attacks that exploit this kind of access
The rule that runs asc_patch_app_preview 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_patch_app_preview, this is the rule to start with:
asc_patch_app_preview 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_patch_app_preview call is checked against it from then on.
Questions about asc_patch_app_preview
RAW step 3 of the three-step upload flow + the only way to tweak previewFrameTimeCode on an existing preview. PATCH with sourceFileChecksum + uploaded=true to commit a reservation, or with previewFrameTimeCode alone to change the poster frame without re-uploading the video. Wire-key gotcha: Swift. 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_patch_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.
asc_patch_app_preview 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_patch_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.
Set action: deny in the PolicyLayer policy for asc_patch_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.
asc_patch_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.
This server
Across the catalogue