asc_list_app_screenshots
List AppScreenshot records under an AppScreenshotSet. Each row carries fileName + fileSize + assetDeliveryState (UPLOAD_COMPLETE / PROCESSING / COMPLETE / FAILED) + a short marker showing whether sourceFileChecksum has been committed. Use to inspect upload progress or to enumerate IDs for deletion.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-app-screenshots.md
What asc_list_app_screenshots does on Appstoreconnect Mcp
AI agents call asc_list_app_screenshots 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_list_app_screenshots is rated Low
This tool retrieves and queries app screenshot metadata including file names, sizes, and upload states. It performs no modifications, deletions, or external operations. While it can enumerate IDs for potential future deletion, the tool itself only reads data. The inspection-focused use case confirms this is a Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'List AppScreenshot records' and 'Use to inspect upload progress or to enumerate IDs'. The verb 'List' and the passive inspection use case indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs asc_list_app_screenshots 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_list_app_screenshots, this is the rule to start with:
asc_list_app_screenshots 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_list_app_screenshots call is checked against it from then on.
Questions about asc_list_app_screenshots
List AppScreenshot records under an AppScreenshotSet. Each row carries fileName + fileSize + assetDeliveryState (UPLOAD_COMPLETE / PROCESSING / COMPLETE / FAILED) + a short marker showing whether sourceFileChecksum has been committed. Use to inspect upload progress or to enumerate IDs for deletion. 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_list_app_screenshots: 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_list_app_screenshots 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_list_app_screenshots 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_list_app_screenshots. 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_list_app_screenshots 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