mindmap_config · Mindmap MCP: Risk & Policy

WHAT IT DOES

What mindmap_config does on Mindmap

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

WHY IT NEEDS A POLICY

Why mindmap_config needs a policy

When arguments are provided, this tool modifies server configuration (decay windows, longevity factor, gamification toggle), making it a Write operation. When called with no args it is read-only, but the tool's primary capability includes modification. Misuse could alter how memory retention and decay work across all AI sessions sharing this server, affecting context persistence — a medium blast radius.

From the tool's definition 'View or change Mind Map settings: decay windows, the promoted longevity factor, and the gamification toggle' — explicitly supports changing configuration parameters

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mindmap_config Rate-limited

mindmap_config 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": {
    "mindmap_config": {
      "limits": [
        {
          "counter": "mindmap_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mindmap, so you can run agents against it safely.

FAQ

Questions about mindmap_config

What does the mindmap_config tool do? +

View or change Mind Map settings: decay windows, the promoted longevity factor, and the gamification toggle. Omit all args to just view current settings. Args (all optional): hot_window_days, warm_window_days, promoted_longevity_factor, gamification. Returns: the effective config. It is categorised as a Write tool in the Mindmap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mindmap_config? +

Register the Mindmap MCP server in PolicyLayer and add a rule for mindmap_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 Mindmap. Nothing to install.

What risk level is mindmap_config? +

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

Can I rate-limit mindmap_config? +

Yes. Add a rate_limit block to the mindmap_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.

How do I block mindmap_config completely? +

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

What MCP server provides mindmap_config? +

mindmap_config is provided by the Mindmap MCP server (@ravi-labs/mindmap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.