asc_upload_asset_chunk
RAW step 2 of the three-step screenshot / preview upload flow. Apple
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-upload-asset-chunk.md
What asc_upload_asset_chunk does on Appstoreconnect Mcp
AI agents use asc_upload_asset_chunk 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_upload_asset_chunk is rated Medium
This tool creates or modifies data (screenshots/preview assets) in a reversible manner. While uploads can impact app listings, they are not destructive (can be replaced or deleted) and do not involve financial transactions or code execution. The medium severity reflects that misuse could deface app store listings but changes are recoverable.
From the tool's definition Tool name contains 'upload' and description indicates 'step 2 of the three-step screenshot / preview upload flow', confirming it modifies data by uploading asset chunks to App Store Connect.
Attacks that exploit this kind of access
The rule that runs asc_upload_asset_chunk 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_upload_asset_chunk, this is the rule to start with:
asc_upload_asset_chunk 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_upload_asset_chunk call is checked against it from then on.
Questions about asc_upload_asset_chunk
RAW step 2 of the three-step screenshot / preview upload flow. Apple. 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_upload_asset_chunk: 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_upload_asset_chunk 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_upload_asset_chunk 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_upload_asset_chunk. 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_upload_asset_chunk 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