xmemo_todo_complete · Openclaw Memory MCP: Risk & Policy

WHAT IT DOES

What xmemo_todo_complete does on Openclaw Memory

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

This tool updates the completion status of a reminder/TODO item, which is a reversible modification of data (Write category). It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely retrieve data (not Read).

From the tool's definition Tool name 'xmemo_todo_complete' and description 'Mark a XMemo reminder as complete by its id' indicate a state change operation that modifies an existing reminder record without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xmemo_todo_complete Rate-limited

xmemo_todo_complete 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": {
    "xmemo_todo_complete": {
      "limits": [
        {
          "counter": "xmemo_todo_complete_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 xmemo_todo_complete

What does the xmemo_todo_complete tool do? +

Mark a XMemo reminder as complete by its id. 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 xmemo_todo_complete? +

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

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

Can I rate-limit xmemo_todo_complete? +

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

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

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

// THE FULL RECORD

xmemo_todo_complete is one line of Openclaw Memory'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 →