asc_get_app_screenshot
Fetch a single AppScreenshot by ID. Returns the upload metadata (fileName, fileSize, sourceFileChecksum), assetDeliveryState, the imageAsset URLs once processed, and — if the reservation has not been committed yet — the uploadOperations[] needed to PUT chunks to Apple storage.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-app-screenshot.md
What asc_get_app_screenshot does on Appstoreconnect Mcp
AI agents call asc_get_app_screenshot to retrieve information from Appstoreconnect Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why asc_get_app_screenshot is rated Low
This tool retrieves screenshot metadata and asset delivery information from App Store Connect without creating, modifying, deleting, or executing any operations. It is purely informational, returning existing data about screenshots. The uploadOperations[] reference is context for incomplete uploads but does not constitute write functionality by this tool itself.
From the tool's definition The tool description explicitly states 'Fetch a single AppScreenshot by ID' and 'Returns' metadata and URLs. The verb 'Fetch' and the read-only nature of retrieving screenshot information with no modification capability indicates a retrieval operation.
Attacks that exploit this kind of access
The rule that runs asc_get_app_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_get_app_screenshot, this is the rule to start with:
asc_get_app_screenshot is read-only, so it stays allowed. 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_get_app_screenshot call is checked against it from then on.
Questions about asc_get_app_screenshot
Fetch a single AppScreenshot by ID. Returns the upload metadata (fileName, fileSize, sourceFileChecksum), assetDeliveryState, the imageAsset URLs once processed, and — if the reservation has not been committed yet — the uploadOperations[] needed to PUT chunks to Apple storage. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_get_app_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_get_app_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the asc_get_app_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_get_app_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_get_app_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