apple_ads_change_history
Who changed what on this Apple Ads account, and when. Call it with start and/or end to get one row per TRANSACTION GROUP — a single user action that may have touched several fields, which is what changeCount counts — with the user, the entity and the event type (CREATE / UPDATE / DELETE). Then pa...
This record as markdown: /tools/hermoso/apple-ads-change-history.md
What apple_ads_change_history does on Hermoso
AI agents call apple_ads_change_history to permanently remove resources in Hermoso, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why apple_ads_change_history is rated Critical
An AI agent that decides to call apple_ads_change_history doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hermoso is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs apple_ads_change_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For apple_ads_change_history, this is the rule to start with:
apple_ads_change_history is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every apple_ads_change_history call is checked against it from then on.
Questions about apple_ads_change_history
Who changed what on this Apple Ads account, and when. Call it with start and/or end to get one row per TRANSACTION GROUP — a single user action that may have touched several fields, which is what changeCount counts — with the user, the entity and the event type (CREATE / UPDATE / DELETE). Then pass a row’s detailId back as detailId to get the field-by-field before and after. THE TIME BOUND IS MANDATORY: Apple answers 400 without one, so pass start (meaning. It is categorised as a Destructive tool in the Hermoso MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hermoso MCP server in PolicyLayer and add a rule for apple_ads_change_history: 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 Hermoso. Nothing to install.
apple_ads_change_history is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the apple_ads_change_history 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 apple_ads_change_history. 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.
apple_ads_change_history is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hermoso, and thousands of servers like it.
Across the catalogue