Low Risk

export_conversation

Export a Claude Code conversation to markdown or JSON format for backup or sharing.

How to control export_conversation ↓

What export_conversation does on Claude Code Toolkit

AI agents call export_conversation to retrieve information from Claude Code Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why export_conversation needs a policy

This tool reads an existing conversation and outputs it in a different format (markdown or JSON). It does not modify, delete, or execute anything — it is a pure read/export operation. Severity is low because the worst-case misuse is leaking conversation content to an unintended destination, but it causes no irreversible changes.

From the tool's definition Export a Claude Code conversation to markdown or JSON format for backup or sharing

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

How to control export_conversation

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for export_conversation:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_conversation": {}
  }
}

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

  1. Create a free account and register Claude Code Toolkit — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about export_conversation

What does the export_conversation tool do? +

Export a Claude Code conversation to markdown or JSON format for backup or sharing. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_conversation? +

Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for export_conversation: 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 Claude Code Toolkit. Nothing to install.

What risk level is export_conversation? +

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

Can I rate-limit export_conversation? +

Yes. Add a rate_limit block to the export_conversation 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 export_conversation completely? +

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

export_conversation is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Code Toolkit tool call.

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

Free to start. No card required.

40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.