This record as markdown: /tools/108yen-memo-mcp/creatememo.md
What createMemo does on Memo
AI agents use createMemo 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 createMemo is rated Medium
This tool creates new memo records in a local LowDB database. Creation of new data is a Write operation. Severity is low because: (1) the operation is reversible (memos can be deleted), (2) the blast radius is limited to a local memo database with no external integrations or financial impact, and (3) misuse would only result in unwanted memo entries that can be cleaned up.
From the tool's definition Tool name is 'createMemo' and description states 'Create a new memo'. The action creates new data in a local database without permanent destructive effects, modifications to existing records, or external side effects.
Attacks that exploit this kind of access
The rule that runs createMemo 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 createMemo, this is the rule to start with:
createMemo 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 createMemo call is checked against it from then on.
Questions about createMemo
Create a new 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 createMemo: 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.
createMemo 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 createMemo 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 createMemo. 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.
createMemo 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