analytics_revoke_tracker
Revoke the API key bound to a tracker. After this, the key is rejected by the ingest endpoints — any pages still embedding it will silently fail to record views. The tracker row stays for audit.
This record as markdown: /tools/com-getmunin-munin/analytics-revoke-tracker.md
What analytics_revoke_tracker does on Munin
AI agents call analytics_revoke_tracker to permanently remove resources in Munin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why analytics_revoke_tracker is rated Critical
Revoking an API key is an irreversible action (the key is permanently invalidated). While the tracker row is retained for audit, the key itself cannot be un-revoked without generating a new one, making this a destructive operation. Misuse could silently break analytics tracking across all pages using that key, with high blast radius for data collection continuity.
From the tool's definition Revoke the API key bound to a tracker. After this, the key is rejected by the ingest endpoints — any pages still embedding it will silently fail to record views.
Attacks that exploit this kind of access
The rule that runs analytics_revoke_tracker safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analytics_revoke_tracker, this is the rule to start with:
analytics_revoke_tracker 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 Munin, apply this rule, and every analytics_revoke_tracker call is checked against it from then on.
Questions about analytics_revoke_tracker
Revoke the API key bound to a tracker. After this, the key is rejected by the ingest endpoints — any pages still embedding it will silently fail to record views. The tracker row stays for audit. It is categorised as a Destructive tool in the Munin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Munin MCP server in PolicyLayer and add a rule for analytics_revoke_tracker: 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 Munin. Nothing to install.
analytics_revoke_tracker 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 analytics_revoke_tracker 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 analytics_revoke_tracker. 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.
analytics_revoke_tracker is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
Across the catalogue