analytics_import

Import analytics

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

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What analytics_import does on Munin

AI agents use analytics_import to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.

RISK

Why analytics_import is rated Medium

Import operations create or modify data records reversibly, fitting the Write category. While the description is sparse, the tool's placement alongside export and read-only analytics tools (list, get, export) and its naming convention suggest it ingests analytics data.

From the tool's definition Tool name 'analytics_import' and description 'Import analytics' indicate data ingestion that creates or modifies analytics records. No delete or destructive language present. Not a query/retrieval operation (Read category).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

analytics_import Rate-limited

analytics_import stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analytics_import": {
      "limits": [
        {
          "counter": "analytics_import_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about analytics_import

What does the analytics_import tool do? +

Import analytics. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on analytics_import? +

Register the Munin MCP server in PolicyLayer and add a rule for analytics_import: 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_import? +

analytics_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit analytics_import? +

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

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

analytics_import 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →