Get details of a specific analytics report request.
AI agents call get_analytics_report_request 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 information about an analytics report request without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal risk if misused by an AI agent—at worst, an agent could access analytics data it shouldn't, but no actual damage or irreversible changes would occur.
From the tool's definition Tool name 'get_analytics_report_request' and description 'Get details of a specific analytics report request' indicate data retrieval with no modification or deletion. The verb 'get' and 'details of' confirm read-only semantics.
Documented attack patterns abuse exactly the kind of access get_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 get_analytics_report_request:
{
"version": "1",
"default": "deny",
"tools": {
"get_analytics_report_request": {}
}
} get_analytics_report_request 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.
Get details of a specific analytics report request. 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 get_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.
get_analytics_report_request 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 get_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 get_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.
get_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.