List all analytics report requests for an app. Shows whether each request is active or stopped due to inactivity.
AI agents call list_analytics_report_requests 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.
This tool retrieves and displays existing analytics report request metadata without modifying, deleting, or executing any operations. It is purely informational, making it a Read category tool with low severity since it only exposes analytics configuration data that an app owner would typically have visibility into.
From the tool's definition Tool name 'list_analytics_report_requests' and description 'List all analytics report requests for an app. Shows whether each request is active or stopped due to inactivity' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_analytics_report_requests 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 list_analytics_report_requests:
{
"version": "1",
"default": "deny",
"tools": {
"list_analytics_report_requests": {}
}
} list_analytics_report_requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all analytics report requests for an app. Shows whether each request is active or stopped due to inactivity. It is categorised as a Read tool in the Asc MCP Server, which means it retrieves data without modifying state.
Register the Asc MCP server in PolicyLayer and add a rule for 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 Asc. Nothing to install.
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 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 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.
list_analytics_report_requests 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.