Mind Map runs fully WITHOUT an LLM. This is opt-in: plug in your OWN provider to unlock smarter features (LLM-assisted persona inference, richer summaries). Security: Mind Map stores only the provider + model name. It NEVER stores your API key — the key is read from your environment (ANTHROPIC_AP...
AI agents use mindmap_llm 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 allows users to write/modify persistent configuration for LLM provider integration. While it doesn't delete data (ruling out Destructive), doesn't execute arbitrary code directly (ruling out Execute), and doesn't move money (ruling out Financial), it does alter stored configuration settings that affect system behavior.
From the tool's definition Tool configures and modifies LLM provider settings (provider, model, baseUrl) that are stored persistently ('Mind Map stores only the provider + model name').
Attacks that exploit this kind of access
Mind Map runs fully WITHOUT an LLM. This is opt-in: plug in your OWN provider to unlock smarter features (LLM-assisted persona inference, richer summaries). Security: Mind Map stores only the provider + model name. It NEVER stores your API key — the key is read from your environment (ANTHROPIC_API_KEY / OPENAI_API_KEY / GOOGLE_API_KEY; ollama needs none). Set the env var yourself. Args (all optional — omit all to just see status): - provider: none | anthropic | openai | google | ollama - model: override the default model - baseUrl: for ollama / self-hosted (default http://localhost:11434) Returns: current provider/model, whether it. 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_llm: 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_llm 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_llm 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_llm. 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_llm 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 →