memory_export

THE RISK

Low Risk

Why memory_export needs a policy

The tool exports (reads/retrieves) stored memory data and serializes it to JSON or CSV format. This is a read/export operation with no indication of modification, deletion, or execution of code. Severity is low as it only reads internal memory state.

From the tool's definition Export memories to JSON or CSV

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 Documcp, 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 Documcp — 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 Documcp tools

Destructive cleanup_agent_artifacts Detect, classify, and clean up artifacts generated by AI coding agents (e.g., TODO.md, PLA Destructive memory_cleanup Clean up old memories Destructive memory_pruning Intelligent memory pruning and optimization Execute change_watcher Watch code changes and trigger documentation drift detection in near real-time. Execute deploy_pages [DEPRECATED — use deploy_site instead] Set up GitHub Pages deployment workflow. This alias Execute deploy_site Set up deployment workflow for GitHub Pages or Vercel with deployment tracking and prefere Execute memory_migration Create and execute migration plans between different memory systems Execute test_local_deployment Test documentation build and local server before deploying to GitHub Pages

All 52 Documcp 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 memories to JSON or CSV. It is categorised as a Read tool in the Documcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_export? +

Register the Docu 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 Documcp. 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 Docu MCP server (tosin2013/documcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Documcp tool call.

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

CHECK YOUR STACK →