AI agents use save_note to create or update resources in Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory environment.
This tool creates or modifies notes in a local knowledge store. It is reversible (notes can be edited or deleted later), so it is Write rather than Destructive. The severity is medium because misuse by an AI agent could result in unwanted notes being saved to the user's personal knowledge base, potentially polluting search results or creating false records, but the impact is limited to this local system and…
From the tool's definition Tool name 'save_note' combined with context of a note-taking/memory MCP server indicates creation or modification of note data. The empty description limits precision, but 'save' typically means persist/create/update operations.
Attacks that exploit this kind of access
save_note. It is categorised as a Write tool in the Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory MCP server in PolicyLayer and add a rule for save_note: 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 Memory. Nothing to install.
save_note 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 save_note 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 save_note. 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.
save_note is provided by the Memory MCP server (shaktisinhchavda/memory-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 →