AI agents use mindmap_persona_set 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 user preferences durably in persistent storage. While reversible (preferences can be changed or deleted), it writes configuration state that affects future AI agent behavior. The incomplete description suggests it sets persona/preference data. Severity is medium because misuse could cause inconvenient behavior changes across sessions, but no data loss or external effects occur.
From the tool's definition Tool name 'mindmap_persona_set' and description 'Save a durable preference' indicate creation or modification of user preference data that persists across sessions.
Attacks that exploit this kind of access
Save a durable preference about how the user works, so future sessions don. 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_persona_set: 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_persona_set 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_persona_set 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_persona_set. 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_persona_set 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 →