memory_export

THE RISK

Low Risk

Why memory_export needs a policy

This tool reads and exports data from the memory store without modifying or deleting anything. It is a bulk data retrieval operation. The severity is medium because it exports the *complete* memory store including tombstoned items, meaning a misuse could expose all stored contextual memories (potentially sensitive LLM interaction history) to an unauthorized party.

From the tool's definition Export the complete memory store as raw JSON, including soft-deleted (tombstoned) items. Useful for backup, migration, or debugging.

Documented attack patterns abuse exactly the kind of access memory_export gives an agent:

POLICY

How to control memory_export

PolicyLayer is an MCP gateway — it sits between your AI agents and Copilot Memory Store, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_export:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_export": {}
  }
}

memory_export is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Copilot Memory Store — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Copilot Memory Store tools

Destructive memory_delete Soft-delete a memory by ID (tombstone). The memory is marked as deleted but remains in sto Destructive memory_purge PERMANENTLY delete memories by id, tag, or substring match. This is destructive and cannot Write memory_write Add, save, store, or remember information to the project memory. Use this when the user wa Read inject_context Inject relevant project context for a coding task. Call this BEFORE starting work to retri Read memory_search Search, find, recall, or look up information from project memory. Use this when the user a Read memory_compress Create a compact Markdown context block from relevant memories, constrained to a character

All 7 Copilot Memory Store tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about memory_export

What does the memory_export tool do? +

Export the complete memory store as raw JSON, including soft-deleted (tombstoned) items. Useful for backup, migration, or debugging. It is categorised as a Read tool in the Copilot Memory Store MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_export? +

Register the Copilot Memory Store MCP server in PolicyLayer and add a rule for memory_export: 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 Copilot Memory Store. Nothing to install.

What risk level is memory_export? +

memory_export is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit memory_export? +

Yes. Add a rate_limit block to the memory_export 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.

How do I block memory_export completely? +

Set action: deny in the PolicyLayer policy for memory_export. 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.

What MCP server provides memory_export? +

memory_export is provided by the Copilot Memory Store MCP server (timothywarner-org/copilot-memory-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Copilot Memory Store tool call.

Start from Copilot Memory Store, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →