Search across all saved context (every tier, every tool) to relocate a past discussion. Read-only — does not change freshness or tiers (use mindmap_resume to actually pull a memory forward). Args: - query (string): keywords; empty string browses by recency - source/tag/tier: optional filters - in...
AI agents call mindmap_search 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 retrieves and queries stored memories with no ability to create, modify, delete, or execute operations. The explicit 'Read-only' designation and lack of write/execute/destructive capabilities make this a straightforward Read category tool.
From the tool's definition Tool description explicitly states 'Read-only — does not change freshness or tiers' and 'Search across all saved context'. Arguments are search filters (query, source/tag/tier, include_archived, limit) with no mutation capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Search across all saved context (every tier, every tool) to relocate a past discussion. Read-only — does not change freshness or tiers (use mindmap_resume to actually pull a memory forward). Args: - query (string): keywords; empty string browses by recency - source/tag/tier: optional filters - include_archived (boolean): include forgotten traces (default false) - limit (number): max results (default 10) Returns: ranked list of matching memories. 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_search: 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_search 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_search 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_search. 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_search 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.
mindmap_search is one line of Mindmap's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →