# updateMemo

Update a memo

Agent View of the PolicyLayer registry record for `updateMemo`. HTML page: https://policylayer.com/tools/108yen-memo-mcp/updatememo

## Facts

- Tool: `updateMemo`
- Server: Memo (`108yen/memo-mcp`) — https://policylayer.com/tools/108yen-memo-mcp.md
- Homepage: https://github.com/108yen/memo-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "updateMemo",
    "arguments": {}
  }
}
```

## Why updateMemo is rated Medium

This tool creates or modifies data reversibly by updating memo records. It does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute). The blast radius is medium because memo corruption could impact users' recorded information, but the effect is limited to a single memo record and is reversible through subsequent updates.

From the tool's own definition: "Tool name is 'updateMemo' and description states 'Update a memo', which modifies existing data in the database."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Memo:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "updateMemo": {
      "limits": [
        {
          "counter": "updatememo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Memo (10)

- `deleteCategory` — Destructive — https://policylayer.com/tools/108yen-memo-mcp/deletecategory.md
- `deleteMemo` — Destructive — https://policylayer.com/tools/108yen-memo-mcp/deletememo.md
- `getCategories` — Read — https://policylayer.com/tools/108yen-memo-mcp/getcategories.md
- `getCategory` — Read — https://policylayer.com/tools/108yen-memo-mcp/getcategory.md
- `getMemo` — Read — https://policylayer.com/tools/108yen-memo-mcp/getmemo.md
- `getMemos` — Read — https://policylayer.com/tools/108yen-memo-mcp/getmemos.md
- `searchMemos` — Read — https://policylayer.com/tools/108yen-memo-mcp/searchmemos.md
- `createCategory` — Write — https://policylayer.com/tools/108yen-memo-mcp/createcategory.md
- `createMemo` — Write — https://policylayer.com/tools/108yen-memo-mcp/creatememo.md
- `updateCategory` — Write — https://policylayer.com/tools/108yen-memo-mcp/updatecategory.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=108yen-memo-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/108yen-memo-mcp
