list_ga4_key_events
List the key events (conversions) configured on a GA4 property — by event NAME, with counting method and whether it is a custom event. Requires property like
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/list-ga4-key-events.md
What list_ga4_key_events does on Samarth Gtm Mcp
AI agents call list_ga4_key_events to retrieve information from Samarth Gtm Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_ga4_key_events is rated Low
This tool queries GA4 configuration metadata (event names, counting methods, custom event flags) with no side effects. It retrieves existing data structures for inspection only. Severity is low because exposure of event configuration carries minimal blast radius—it is non-destructive intelligence gathering about analytics setup, not account modification or financial impact.
From the tool's definition Tool description states 'List the key events' and 'Requires property' — a read-only query operation that retrieves configured events without modification.
Attacks that exploit this kind of access
The rule that runs list_ga4_key_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_ga4_key_events, this is the rule to start with:
list_ga4_key_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every list_ga4_key_events call is checked against it from then on.
Questions about list_ga4_key_events
List the key events (conversions) configured on a GA4 property — by event NAME, with counting method and whether it is a custom event. Requires property like. It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for list_ga4_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 Samarth Gtm Mcp. Nothing to install.
list_ga4_key_events 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_ga4_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.
Set action: deny in the PolicyLayer policy for list_ga4_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.
list_ga4_key_events is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Samarth Gtm, and thousands of servers like it.
This server
Across the catalogue