Create a new analytics report request for an app. Use ONGOING for continuous reports or ONE_TIME_SNAPSHOT for a single snapshot. Reports take time to generate after creation.
AI agents use create_analytics_report_request to create or update resources in Asc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Asc environment.
This tool creates a new resource (analytics report request) which is a reversible modification of system state. It does not execute arbitrary code, delete data irreversibly, or move money. While it initiates report generation, the actual report data retrieval is handled by separate read tools (get_analytics_report_request, download_analytics_report_segment).
From the tool's definition create_analytics_report_request creates a new analytics report request (stated in description). This is a creation action that modifies state in the App Store Connect system by adding a new report request resource.
Documented attack patterns abuse exactly the kind of access create_analytics_report_request gives an agent:
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 create_analytics_report_request:
{
"version": "1",
"default": "deny",
"tools": {
"create_analytics_report_request": {
"limits": [
{
"counter": "create_analytics_report_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_analytics_report_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new analytics report request for an app. Use ONGOING for continuous reports or ONE_TIME_SNAPSHOT for a single snapshot. Reports take time to generate after creation. It is categorised as a Write tool in the Asc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Asc MCP server in PolicyLayer and add a rule for create_analytics_report_request: 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.
create_analytics_report_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_analytics_report_request 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 create_analytics_report_request. 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.
create_analytics_report_request 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.
Start from Asc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Asc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.