AI agents use mindmap_link 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.
The tool creates or modifies relational connections between existing memory objects. This is reversible (links can be removed) and has no side effects beyond updating internal state. It does not execute code, delete data, move money, or trigger external systems. The 'lightweight' descriptor further suggests this is a simple metadata write operation.
From the tool's definition Tool description states it 'Connect[s] two memories' and is described as a linking operation that creates 'bidirectional' references between memories.
Attacks that exploit this kind of access
Connect two memories so related threads (e.g. planning in Chat + code in Claude Code) cross-reference each other. Bidirectional. This is the lightweight. 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_link: 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_link 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_link 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_link. 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_link 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 →