ga_run_report
Run a GA4 report with configurable dimensions, metrics, date range, ordering, and safe dataset controls. Estimates row count first; returns a warning above row_warning_threshold (default 2500). Use ga_search_schema to discover dimension/metric apiNames.
This record as markdown: /tools/freshdesk/ga-run-report.md
What ga_run_report does on Freshdesk
AI agents invoke ga_run_report to trigger actions in Freshdesk. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ga_run_report is rated High
This tool actively runs/executes a report query against GA4. While it only reads analytics data (no data modification), the 'run' verb and configurable query execution place it in the Execute category rather than pure Read. It triggers an external operation (GA4 API call) whose scope depends on arguments. Severity is medium as misuse could expose sensitive analytics data or consume API quota, but no data is modified.
From the tool's definition 'Run a GA4 report' — executes a query/report against Google Analytics 4 with configurable dimensions, metrics, date range, ordering, and row count estimation
Attacks that exploit this kind of access
The rule that runs ga_run_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ga_run_report, this is the rule to start with:
ga_run_report stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every ga_run_report call is checked against it from then on.
Questions about ga_run_report
Run a GA4 report with configurable dimensions, metrics, date range, ordering, and safe dataset controls. Estimates row count first; returns a warning above row_warning_threshold (default 2500). Use ga_search_schema to discover dimension/metric apiNames. It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Freshdesk MCP server in PolicyLayer and add a rule for ga_run_report: 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 Freshdesk. Nothing to install.
ga_run_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ga_run_report 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 ga_run_report. 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.
ga_run_report is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
Across the catalogue