AI agents call mindmap_get to retrieve information from Mindmap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation with no side effects. It queries a memory store by ID and returns the full thread content. The explicit 'Read-only' designation and absence of any write, delete, or execute semantics place it clearly in the Read category. Blast radius is minimal—misuse would only allow an AI to access existing memory data it may not have permission to see, not modify or destroy it.
From the tool's definition Tool description explicitly states 'Fetch the full content of one memory by id. Read-only (does not change freshness).' The operation retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
Fetch the full content of one memory by id. Read-only (does not change freshness). Args: id (string). Returns: the full thread. It is categorised as a Read tool in the Mindmap MCP Server, which means it retrieves data without modifying state.
Register the Mindmap MCP server in PolicyLayer and add a rule for mindmap_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mindmap_get 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_get. 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_get 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 →