memory_log_conversation_append · OpenClaw Memory MCP

WHAT IT DOES

What memory_log_conversation_append does on OpenClaw Memory

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

WHY IT NEEDS A POLICY

Why memory_log_conversation_append needs a policy

Based on the tool name and server context, this tool likely appends conversation data to local Markdown files, which is a reversible write operation. The server description states it 'automatically records AI conversation turns and code changes to local Markdown files.' The 'append' suffix strongly implies writing/adding data rather than reading or deleting.

From the tool's definition Tool name 'memory_log_conversation_append' — 'append' suggests adding data to existing records; 'log_conversation' suggests writing conversation data to Markdown files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_log_conversation_append Rate-limited

memory_log_conversation_append 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_log_conversation_append": {
      "limits": [
        {
          "counter": "memory_log_conversation_append_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 OpenClaw Memory, so you can run agents against it safely.

FAQ

Questions about memory_log_conversation_append

What does the memory_log_conversation_append tool do? +

memory_log_conversation_append. It is categorised as a Write tool in the OpenClaw Memory 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_log_conversation_append? +

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

What risk level is memory_log_conversation_append? +

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

Can I rate-limit memory_log_conversation_append? +

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

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

memory_log_conversation_append is provided by the OpenClaw Memory MCP server (liuhao6741/openclaw-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.