asc_upload_screenshot
Composite tool. Reads localFilePath from disk, reserves an AppScreenshot under the given set with fileName + fileSize derived from the file, PUTs every uploadOperation chunk to Apple storage in sequence, then commits with sourceFileChecksum (md5 hex) + uploaded=true. Returns the final committed r...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-upload-screenshot.md
What asc_upload_screenshot does on Appstoreconnect Mcp
AI agents use asc_upload_screenshot 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_screenshot is rated Medium
The tool creates a new screenshot resource in App Store Connect and uploads file content to Apple's storage, constituting irreversible data creation. While it doesn't delete data (not Destructive) or execute arbitrary code (not Execute), it modifies the app's store listing by adding media assets.
From the tool's definition Tool 'reserves an AppScreenshot', 'PUTs every uploadOperation chunk to Apple storage', and 'commits with sourceFileChecksum + uploaded=true'. These are create/modify operations that persist data to App Store Connect.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs asc_upload_screenshot 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_screenshot, this is the rule to start with:
asc_upload_screenshot 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_screenshot call is checked against it from then on.
Questions about asc_upload_screenshot
Composite tool. Reads localFilePath from disk, reserves an AppScreenshot under the given set with fileName + fileSize derived from the file, PUTs every uploadOperation chunk to Apple storage in sequence, then commits with sourceFileChecksum (md5 hex) + uploaded=true. Returns the final committed resource + a per-chunk summary. Tilde paths (~/...) are expanded. For manual control over each step, use the raw asc_post_app_screenshot + asc_upload_asset_chunk + asc_patch_app_screenshot tools instead. 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_screenshot: 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_screenshot 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_screenshot 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_screenshot. 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_screenshot 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