memory_export · Sekha MCP Server MCP: Risk & Policy

WHAT IT DOES

What memory_export does on Sekha MCP Server

AI agents use memory_export to create or update resources in Sekha MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sekha MCP Server environment.

WHY IT NEEDS A POLICY

Why memory_export needs a policy

The tool exports memory data to external formats, which modifies state by creating new artifacts (files or serialized outputs). This is a Write operation rather than Read because it generates and outputs data in a new form. It's not Destructive because the original data remains intact.

From the tool's definition Tool description states 'Export conversation to JSON or Markdown format for backup or external use' — this creates new files/outputs by serializing data, which is a write operation (data is materialized in a new format/location).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_export Rate-limited

memory_export stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_export": {
      "limits": [
        {
          "counter": "memory_export_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sekha MCP Server, so you can run agents against it safely.

FAQ

Questions about memory_export

What does the memory_export tool do? +

Export conversation to JSON or Markdown format for backup or external use. It is categorised as a Write tool in the Sekha MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_export? +

Register the Sekha MCP Server 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 Sekha MCP Server. Nothing to install.

What risk level is memory_export? +

memory_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 Sekha MCP Server MCP server (sekha-ai/sekha-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.