export_static_memory_files · OpenMemBrain MCP: Risk & Policy

WHAT IT DOES

What export_static_memory_files does on OpenMemBrain

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

WHY IT NEEDS A POLICY

Why export_static_memory_files needs a policy

The tool creates or generates new files (Write category), which are modifications to the file system. While file generation is reversible and does not destroy data, it can overwrite existing files and affects the AI coding environment by creating instruction files that guide agent behavior.

From the tool's definition Tool description states it 'Generate[s]' instruction files including AGENTS.md, CLAUDE.md, and project-memory.md — creating or writing files to disk.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_static_memory_files Rate-limited

export_static_memory_files 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": {
    "export_static_memory_files": {
      "limits": [
        {
          "counter": "export_static_memory_files_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 OpenMemBrain, so you can run agents against it safely.

FAQ

Questions about export_static_memory_files

What does the export_static_memory_files tool do? +

Generate fallback instruction files such as AGENTS.md, CLAUDE.md, Copilot instructions, Cursor rules, and docs/ai/project-memory.md. It is categorised as a Write tool in the OpenMemBrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_static_memory_files? +

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

What risk level is export_static_memory_files? +

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

Can I rate-limit export_static_memory_files? +

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

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

export_static_memory_files is provided by the OpenMemBrain MCP server (mohamadalhusseinie/openmembrain). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

export_static_memory_files is one line of OpenMemBrain's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →