asc_download_analytics_report_segment
Fetch a segment URL from asc_list_analytics_report_segments (pre-signed — fetched WITHOUT the ASC auth header; the signature lives in the URL) and gunzip the CSV. Returns header + row preview; saveTo writes the full decoded CSV to disk. Expired URL → re-list segments for a fresh one.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-download-analytics-report-segment.md
What asc_download_analytics_report_segment does on Appstoreconnect Mcp
AI agents call asc_download_analytics_report_segment 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_download_analytics_report_segment is rated Low
This tool retrieves pre-generated analytics reports in CSV format. The core operation is fetching and decompressing data for inspection. While it can persist data to disk via saveTo, writing data locally from a read operation is a secondary effect that does not constitute data creation or modification in the application itself.
From the tool's definition Tool description states it 'Fetch[es] a segment URL' and 'gunzip[s] the CSV' and 'Returns header + row preview'. The saveTo parameter writes to disk but the primary action is retrieving and reading analytics data.
Attacks that exploit this kind of access
The rule that runs asc_download_analytics_report_segment 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_download_analytics_report_segment, this is the rule to start with:
asc_download_analytics_report_segment 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_download_analytics_report_segment call is checked against it from then on.
Questions about asc_download_analytics_report_segment
Fetch a segment URL from asc_list_analytics_report_segments (pre-signed — fetched WITHOUT the ASC auth header; the signature lives in the URL) and gunzip the CSV. Returns header + row preview; saveTo writes the full decoded CSV to disk. Expired URL → re-list segments for a fresh one. 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_download_analytics_report_segment: 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_download_analytics_report_segment 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_download_analytics_report_segment 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_download_analytics_report_segment. 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_download_analytics_report_segment 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