asc_list_app_event_screenshots

List AppEventScreenshot records under an AppEventLocalization. Each row carries fileName + fileSize + the asset slot (EVENT_CARD / EVENT_DETAILS_PAGE) + assetDeliveryState (UPLOAD_COMPLETE / PROCESSING / COMPLETE / FAILED). Use to inspect upload progress or to enumerate IDs.

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-app-event-screenshots.md

What asc_list_app_event_screenshots does on Appstoreconnect Mcp

AI agents call asc_list_app_event_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_event_screenshots is rated Low

This tool retrieves and queries AppEventScreenshot records from App Store Connect without modifying, deleting, or executing external operations. The functionality is purely informational—listing files, their metadata (fileName, fileSize, asset slot, delivery state), and their IDs. No side effects occur from calling this tool, making it a Read category with low severity risk.

From the tool's definition Tool description states it 'List[s]' records and is used 'to inspect upload progress or to enumerate IDs'.

Questions about asc_list_app_event_screenshots

What does the asc_list_app_event_screenshots tool do? +

List AppEventScreenshot records under an AppEventLocalization. Each row carries fileName + fileSize + the asset slot (EVENT_CARD / EVENT_DETAILS_PAGE) + assetDeliveryState (UPLOAD_COMPLETE / PROCESSING / COMPLETE / FAILED). Use to inspect upload progress or to enumerate IDs. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on asc_list_app_event_screenshots? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_list_app_event_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.

What risk level is asc_list_app_event_screenshots? +

asc_list_app_event_screenshots is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit asc_list_app_event_screenshots? +

Yes. Add a rate_limit block to the asc_list_app_event_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.

How do I block asc_list_app_event_screenshots completely? +

Set action: deny in the PolicyLayer policy for asc_list_app_event_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.

What MCP server provides asc_list_app_event_screenshots? +

asc_list_app_event_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appstoreconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.