asc_list_analytics_report_segments
GET /v1/analyticsReportInstances/{id}/segments — the downloadable chunks of one instance: checksum, sizeInBytes, and a PRE-SIGNED TIME-LIMITED url. Download promptly with asc_download_analytics_report_segment (pass the URL through verbatim); if a URL expires, re-list segments for fresh ones.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-analytics-report-segments.md
What asc_list_analytics_report_segments does on Appstoreconnect Mcp
AI agents call asc_list_analytics_report_segments 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_analytics_report_segments is rated Low
This is a pure retrieval/query operation that returns segment metadata and pre-signed URLs without altering any data. While pre-signed URLs are included, the tool itself only lists and provides access to existing data. The actual download is a separate tool (asc_download_analytics_report_segment). No side effects, reversibility concerns, code execution, or financial implications exist.
From the tool's definition Tool lists analytics report segments with metadata (checksum, sizeInBytes, URL) for download. The description explicitly states GET /v1/analyticsReportInstances/{id}/segments and uses 'downloadable chunks' and 'list segments' terminology.
Attacks that exploit this kind of access
The rule that runs asc_list_analytics_report_segments 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_analytics_report_segments, this is the rule to start with:
asc_list_analytics_report_segments 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_analytics_report_segments call is checked against it from then on.
Questions about asc_list_analytics_report_segments
GET /v1/analyticsReportInstances/{id}/segments — the downloadable chunks of one instance: checksum, sizeInBytes, and a PRE-SIGNED TIME-LIMITED url. Download promptly with asc_download_analytics_report_segment (pass the URL through verbatim); if a URL expires, re-list segments for fresh ones. 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_analytics_report_segments: 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_analytics_report_segments 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_analytics_report_segments 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_analytics_report_segments. 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_analytics_report_segments 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