AI agents use mindmap_import 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.
This tool creates and modifies data in the local Mind Map database by importing session records. While it performs a read operation (scanning history), its primary action is to write/create new entries into the stored memory system. It is reversible (imported data can be deleted or overwritten via mindmap_forget or updates), so it does not qualify as Destructive.
From the tool's definition Tool imports and creates new sessions/data entries into local Mind Map storage: 'import any NEW sessions into Mind Map'.
Attacks that exploit this kind of access
Scan your local AI-tool history and import any NEW sessions into Mind Map — across Claude Code, Cursor, Copilot, and Cowork. Use this when the user says things like. 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.
Register the Mindmap MCP server in PolicyLayer and add a rule for mindmap_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 Mindmap. Nothing to install.
mindmap_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mindmap_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.
Set action: deny in the PolicyLayer policy for mindmap_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.
mindmap_import 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →