propose_memory_from_session · OpenMemBrain MCP

WHAT IT DOES

What propose_memory_from_session does on OpenMemBrain

AI agents use propose_memory_from_session 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 propose_memory_from_session needs a policy

This tool creates and modifies memory records autonomously ('auto-save') and queues data for storage. While it performs analysis and filtering (which are Read-like), the core action is irreversible creation/modification of persistent memory state. It does not execute arbitrary code, delete data, or move money.

From the tool's definition Tool description states 'auto-save low-risk memory' and 'queue important candidates', which involve creating or modifying memory records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

propose_memory_from_session Rate-limited

propose_memory_from_session 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": {
    "propose_memory_from_session": {
      "limits": [
        {
          "counter": "propose_memory_from_session_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 propose_memory_from_session

What does the propose_memory_from_session tool do? +

Analyze a session transcript or summary, reject unsafe/noisy content, auto-save low-risk memory, and queue important candidates. 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 propose_memory_from_session? +

Register the OpenMemBrain MCP server in PolicyLayer and add a rule for propose_memory_from_session: 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 propose_memory_from_session? +

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

Can I rate-limit propose_memory_from_session? +

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

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

propose_memory_from_session 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.