asc_list_analytics_report_instances
GET /v1/analyticsReports/{id}/instances — the dated materializations of one report, one row per (granularity, processingDate). Filter granularity DAILY/WEEKLY/MONTHLY and/or processingDate (YYYY-MM-DD). Take an instance ID into asc_list_analytics_report_segments. Empty within ~48h of creating the...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-analytics-report-instances.md
What asc_list_analytics_report_instances does on Appstoreconnect Mcp
AI agents call asc_list_analytics_report_instances 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_instances is rated Low
This tool retrieves analytics data with standard query parameters (filtering by date and granularity). It performs a read-only query operation with no side effects, no data modification, no code execution, and no financial impact. The normal ~48h delay in data availability is consistent with standard reporting lag, not an indicator of active operations.
From the tool's definition Tool description indicates GET request that retrieves and lists dated analytics report instances with filtering by granularity and processingDate. No modification, deletion, or side effects are mentioned. Core verbs are 'list' and 'GET'.
Attacks that exploit this kind of access
The rule that runs asc_list_analytics_report_instances 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_instances, this is the rule to start with:
asc_list_analytics_report_instances 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_instances call is checked against it from then on.
Questions about asc_list_analytics_report_instances
GET /v1/analyticsReports/{id}/instances — the dated materializations of one report, one row per (granularity, processingDate). Filter granularity DAILY/WEEKLY/MONTHLY and/or processingDate (YYYY-MM-DD). Take an instance ID into asc_list_analytics_report_segments. Empty within ~48h of creating the request is normal. 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_instances: 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_instances 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_instances 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_instances. 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_instances 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