Update an existing memory by ID or by context match. Use this when the user wants to modify a memory. Can specify either: - id: Direct memory ID (from memory_list) - context: A description of the memory to update (will find best match) At least one of id or context must be provided.
AI agents use memory_update to create or update resources in Cursor Memory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cursor Memory MCP Server environment.
This tool modifies existing data reversibly—memories can be updated again or deleted. It does not execute arbitrary code, delete irreversibly, move money, or perform destructive operations. The severity is medium because an AI agent could modify important user preferences or context if context-matching is imprecise, but the operation is reversible and scoped to a specific memory record rather than bulk data.
From the tool's definition The tool description explicitly states it "Update[s] an existing memory" and supports "modify a memory", which are write operations.
Attacks that exploit this kind of access
Update an existing memory by ID or by context match. Use this when the user wants to modify a memory. Can specify either: - id: Direct memory ID (from memory_list) - context: A description of the memory to update (will find best match) At least one of id or context must be provided. It is categorised as a Write tool in the Cursor Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cursor Memory MCP Server MCP server in PolicyLayer and add a rule for memory_update: 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 Cursor Memory MCP Server. Nothing to install.
memory_update 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 memory_update 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 memory_update. 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.
memory_update is provided by the Cursor Memory MCP Server MCP server (willard-jana/cursor-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 →