ga_list_key_events

List all key events (formerly conversions) configured on a GA4 property.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/freshdesk/ga-list-key-events.md

WHAT IT DOES

What ga_list_key_events does on Freshdesk

AI agents call ga_list_key_events to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ga_list_key_events is rated Low

This tool queries and retrieves GA4 key events configuration data without creating, modifying, executing operations, or deleting anything. It is a pure read operation with minimal security risk if misused by an AI agent.

From the tool's definition Tool name contains 'list' and description states 'List all key events' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ga_list_key_events 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_list_key_events, this is the rule to start with:

ga_list_key_events Allowed

ga_list_key_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ga_list_key_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every ga_list_key_events call is checked against it from then on.

FAQ

Questions about ga_list_key_events

What does the ga_list_key_events tool do? +

List all key events (formerly conversions) configured on a GA4 property. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ga_list_key_events? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for ga_list_key_events: 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.

What risk level is ga_list_key_events? +

ga_list_key_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ga_list_key_events? +

Yes. Add a rate_limit block to the ga_list_key_events 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.

How do I block ga_list_key_events completely? +

Set action: deny in the PolicyLayer policy for ga_list_key_events. 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.

What MCP server provides ga_list_key_events? +

ga_list_key_events 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.

KEEP EXPLORING

More on Freshdesk, and thousands of servers like it.

This server

All 422 Freshdesk tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →