Delete an analytics report request. This stops report generation and removes access to existing reports.
AI agents call delete_analytics_report_request to permanently remove resources in Asc — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation that destroys analytics reports and terminates report generation. Once deleted, the report request and its data cannot be recovered. This is the defining characteristic of Destructive actions. While it does not move money directly, it could impact business intelligence and decision-making for app publishers.
From the tool's definition Tool name contains 'delete' and description states it 'stops report generation and removes access to existing reports' — this irreversibly removes data and access.
Documented attack patterns abuse exactly the kind of access delete_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 delete_analytics_report_request:
{
"version": "1",
"default": "deny",
"hide": [
"delete_analytics_report_request"
]
} delete_analytics_report_request disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an analytics report request. This stops report generation and removes access to existing reports. It is categorised as a Destructive tool in the Asc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Asc MCP server in PolicyLayer and add a rule for delete_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.
delete_analytics_report_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.