ga_search_change_history_events
Search the change history (created/updated/deleted) for a GA4 property. Uses the v1alpha admin API; structure may evolve over time.
This record as markdown: /tools/freshdesk/ga-search-change-history-events.md
What ga_search_change_history_events does on Freshdesk
AI agents call ga_search_change_history_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.
Why ga_search_change_history_events is rated Low
This tool queries historical change events in Google Analytics 4, which is a read-only operation with no side effects. It retrieves audit/change log data without creating, modifying, or deleting any resources. The low severity reflects minimal blast radius—an AI misusing this tool would only retrieve potentially sensitive configuration history, not modify production settings or delete data.
From the tool's definition Tool name and description indicate it 'Search[es] the change history' — a retrieval operation. The description explicitly references searching for events (created/updated/deleted state changes), not performing any modifications or deletions.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs ga_search_change_history_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_search_change_history_events, this is the rule to start with:
ga_search_change_history_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 Freshdesk, apply this rule, and every ga_search_change_history_events call is checked against it from then on.
Questions about ga_search_change_history_events
Search the change history (created/updated/deleted) for a GA4 property. Uses the v1alpha admin API; structure may evolve over time. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for ga_search_change_history_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.
ga_search_change_history_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 ga_search_change_history_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 ga_search_change_history_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.
ga_search_change_history_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.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue