The opt-in gamified curation surface. Reports a cleanliness score — the share of memory that is still live (hot+warm) vs stale — which rewards pruning, not hoarding. Also lists stale candidates worth a tidy pass. Args: none. Returns: health report.
AI agents call mindmap_health 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.
mindmap_health is a diagnostic/monitoring tool that retrieves and reports metrics about the state of stored memory. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. The mention of 'pruning' is aspirational context about user behavior, not what the tool itself does — the tool only reports candidates, it does not perform deletion.
From the tool's definition Tool description states it 'Reports a cleanliness score' and 'lists stale candidates' — purely informational operations that query existing memory state without modifying, deleting, or executing external operations. No arguments and returns a report only.
Attacks that exploit this kind of access
The opt-in gamified curation surface. Reports a cleanliness score — the share of memory that is still live (hot+warm) vs stale — which rewards pruning, not hoarding. Also lists stale candidates worth a tidy pass. Args: none. Returns: health report. 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_health: 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_health 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_health 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_health. 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_health 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 →