Export memories to JSON format with all metadata and embeddings.
AI agents call export_memories to retrieve information from ThoughtMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and exports stored memory data (including metadata and embeddings) into JSON format. It is a data retrieval operation with no side effects. Severity is medium because the exported data could contain sensitive cognitive/memory content including embeddings, which could expose private or proprietary information if misused.
From the tool's definition Export memories to JSON format with all metadata and embeddings
Attacks that exploit this kind of access
Export memories to JSON format with all metadata and embeddings. It is categorised as a Read tool in the ThoughtMCP MCP Server, which means it retrieves data without modifying state.
Register the Thought MCP server in PolicyLayer and add a rule for export_memories: 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 ThoughtMCP. Nothing to install.
export_memories 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 export_memories 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 export_memories. 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.
export_memories is provided by the Thought MCP server (keyurgolani/thoughtmcp). 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 →