asc_list_analytics_report_requests
GET /v1/apps/{id}/analyticsReportRequests — the existing requests (at most one ONGOING + one ONE_TIME_SNAPSHOT). stoppedDueToInactivity=true on an ONGOING request means Apple auto-paused it; delete + recreate to resume.
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-list-analytics-report-requests.md
What asc_list_analytics_report_requests does on Appstoreconnect Mcp
AI agents call asc_list_analytics_report_requests 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_requests is rated Low
This tool queries App Store Connect to retrieve analytics report request status. It has read-only semantics (GET HTTP method, list operation) with no side effects. The mention of deletion context is informational only—the tool itself does not delete or modify data. Blast radius is minimal as it only exposes metadata about previously configured analytics requests.
From the tool's definition Tool performs GET operation to list existing analytics report requests; description explicitly states it retrieves/queries data without modification ('the existing requests'). No create, update, delete, or execute operations are performed.
Attacks that exploit this kind of access
The rule that runs asc_list_analytics_report_requests 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_requests, this is the rule to start with:
asc_list_analytics_report_requests 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_requests call is checked against it from then on.
Questions about asc_list_analytics_report_requests
GET /v1/apps/{id}/analyticsReportRequests — the existing requests (at most one ONGOING + one ONE_TIME_SNAPSHOT). stoppedDueToInactivity=true on an ONGOING request means Apple auto-paused it; delete + recreate to resume. 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_requests: 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_requests 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_requests 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_requests. 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_requests 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