list_analytics_report_instances

List report instances (dated snapshots) for an analytics report. Each instance represents data for a specific processing date. Can filter by granularity (DAILY, WEEKLY, MONTHLY) and processing date.

ServerAsc
CategoryRead

How to control list_analytics_report_instances ↓

WHAT IT DOES

What list_analytics_report_instances does on Asc

AI agents call list_analytics_report_instances to retrieve information from Asc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why list_analytics_report_instances needs a policy

This tool retrieves analytics report snapshots for inspection purposes only. It queries existing data without creating, modifying, deleting, or executing any side effects. The filtering capability (by granularity and date) is a standard query parameter, not a write or execute operation. Even though it accesses App Store Connect data, the read-only nature and low blast radius if misused classify it as low severity.

From the tool's definition Tool description explicitly states 'List report instances' and 'Can filter by...processing date' — these are query operations with no modification or deletion of data. The verb 'list' and 'filter' are typical Read operations.

Documented attack patterns abuse exactly the kind of access list_analytics_report_instances gives an agent:

POLICY

How to control list_analytics_report_instances

PolicyLayer is an MCP gateway — it sits between your AI agents and Asc, and nothing reaches the server without passing your rules. This is the rule we recommend for list_analytics_report_instances:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_analytics_report_instances": {}
  }
}

list_analytics_report_instances is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Asc — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Asc tools

Destructive delete_analytics_report_request Delete an analytics report request. This stops report generation and removes access to exi Write create_analytics_report_request Create a new analytics report request for an app. Use ONGOING for continuous reports or ON Read download_analytics_report_segment Download and parse an analytics report segment from its pre-signed URL. The segment data i Read get_analytics_report_request Get details of a specific analytics report request. Read get_app_perf_metrics Get performance and power metrics for an app (e.g., launch time, memory, battery, hangs). Read get_build_perf_metrics Get performance and power metrics for a specific build. Same metric types as get_app_perf_ Read get_finance_report Download and parse a finance report from App Store Connect. Returns financial report data Read get_sales_report Download and parse a sales report from App Store Connect. Returns tab-delimited report dat

All 14 Asc tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_analytics_report_instances

What does the list_analytics_report_instances tool do? +

List report instances (dated snapshots) for an analytics report. Each instance represents data for a specific processing date. Can filter by granularity (DAILY, WEEKLY, MONTHLY) and processing date. It is categorised as a Read tool in the Asc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_analytics_report_instances? +

Register the Asc MCP server in PolicyLayer and add a rule for 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 Asc. Nothing to install.

What risk level is list_analytics_report_instances? +

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

Can I rate-limit list_analytics_report_instances? +

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

How do I block list_analytics_report_instances completely? +

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

What MCP server provides list_analytics_report_instances? +

list_analytics_report_instances is provided by the Asc MCP server (asc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Asc tool call.

Start from Asc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

14 Asc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.