AI agents use create_memo_comment to create or update resources in Memos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memos environment.
This tool creates new comment data associated with a memo, which is a Write operation. It does not execute arbitrary code, delete data, move money, or cause irreversible changes. Comments can typically be edited or deleted later. Severity is low because misuse would only add unwanted comments, which are easily removable and have limited blast radius.
From the tool's definition Tool name 'create_memo_comment' and description indicate creation of a comment ("创建一个评论" = 'create a comment'). This is a reversible write operation that adds content to an existing memo.
Attacks that exploit this kind of access
在指定的备忘录下创建一个评论,提供内容和可见性设置. It is categorised as a Write tool in the Memos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memos MCP server in PolicyLayer and add a rule for create_memo_comment: 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 Memos. Nothing to install.
create_memo_comment 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 create_memo_comment 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 create_memo_comment. 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.
create_memo_comment is provided by the Memos MCP server (yuzhi-jiang/memos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →