Edit a memory — the human curation moment. Trim a stale summary, refine key points, retitle, or retag. Any omitted field is left unchanged. Set append=true to append to summary/key_points instead of replacing. Args: id, title?, summary?, key_points?, tags?, append (default false). Returns: the up...
AI agents use mindmap_update 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 or modifies data without permanent deletion. Updates to memory summaries, titles, tags, and key points are reversible (can be edited again or reverted). The 'append' parameter enables additive modifications rather than destructive ones.
From the tool's definition Tool explicitly performs edit/update operations on memory data: 'Edit a memory', 'Trim a stale summary, refine key points, retitle, or retag'.
Attacks that exploit this kind of access
Edit a memory — the human curation moment. Trim a stale summary, refine key points, retitle, or retag. Any omitted field is left unchanged. Set append=true to append to summary/key_points instead of replacing. Args: id, title?, summary?, key_points?, tags?, append (default false). Returns: the updated thread. 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_update: 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_update 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_update 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_update. 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_update 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 →