analytics_list_trackers

List analytics trackers for the current org with their key prefix, allowed origins, and revocation state. Plaintext keys are never returned; rotate via

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/analytics-list-trackers.md

WHAT IT DOES

What analytics_list_trackers does on Munin

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

RISK

Why analytics_list_trackers is rated Low

This tool retrieves and displays metadata about analytics trackers (key prefix, allowed origins, revocation state) without modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius—an agent listing trackers cannot cause harm beyond information disclosure of non-sensitive metadata.

From the tool's definition Tool name 'analytics_list_trackers' and description 'List analytics trackers for the current org' explicitly performs a list/query operation. Description confirms 'Plaintext keys are never returned' (read-only, no secrets exposed).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

analytics_list_trackers Allowed

analytics_list_trackers 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": {
    "analytics_list_trackers": {}
  }
}

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

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

FAQ

Questions about analytics_list_trackers

What does the analytics_list_trackers tool do? +

List analytics trackers for the current org with their key prefix, allowed origins, and revocation state. Plaintext keys are never returned; rotate via. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analytics_list_trackers? +

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

What risk level is analytics_list_trackers? +

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

Can I rate-limit analytics_list_trackers? +

Yes. Add a rate_limit block to the analytics_list_trackers 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 analytics_list_trackers completely? +

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

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

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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