This record as markdown: /tools/com-getmunin-munin/analytics-export-config.md
What analytics_export_config does on Munin
AI agents call analytics_export_config 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.
Why analytics_export_config is rated Low
The tool name 'analytics_export_config' and the truncated description 'Export this org\' suggest this tool retrieves and exports analytics configuration settings for the organization. This is a Read operation as it exports/retrieves existing configuration data without modifying it. Confidence is moderate due to the truncated description leaving ambiguity about full functionality.
From the tool's definition 'Export this org\' - description appears truncated, but 'export' in the context of analytics configuration suggests reading/exporting configuration data
Attacks that exploit this kind of access
The rule that runs analytics_export_config 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_export_config, this is the rule to start with:
analytics_export_config 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 Munin, apply this rule, and every analytics_export_config call is checked against it from then on.
Questions about analytics_export_config
Export this org\. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for analytics_export_config: 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_export_config 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 analytics_export_config 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_export_config. 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_export_config 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.
This server
Across the catalogue