This record as markdown: /tools/108yen-memo-mcp/updatememo.md
What updateMemo does on Memo
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.
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 definition Tool name is 'updateMemo' and description states 'Update a memo', which modifies existing data in the database.
Attacks that exploit this kind of access
The rule that runs updateMemo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Memo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updateMemo, this is the rule to start with:
updateMemo 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Memo, apply this rule, and every updateMemo call is checked against it from then on.
Questions about updateMemo
Update a memo. It is categorised as a Write tool in the Memo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memo MCP server in PolicyLayer and add a rule for updateMemo: 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 Memo. Nothing to install.
updateMemo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the updateMemo 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.
Set action: deny in the PolicyLayer policy for updateMemo. 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.
updateMemo is provided by the Memo MCP server (108yen/memo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Memo, and thousands of servers like it.
This server
Across the catalogue