Update memory Args: memory_id: Memory ID content: New content user_id: User identifier agent_id: Agent identifier metadata: Updated metadata Returns: JSON formatted string
AI agents use update_memory to create or update resources in Mcp Oceanbase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Oceanbase environment.
The tool creates or modifies data reversibly—it updates memory entries rather than permanently deleting them. This is characteristic of Write operations. Severity is medium because unauthorized memory updates could corrupt application state, alter user context, or cause logic errors, but effects are not permanent and can be rolled back.
From the tool's definition Tool named 'update_memory' with description 'Update memory' that modifies existing memory records by taking memory_id, content, user_id, agent_id, and metadata parameters and returning a JSON response.
Documented attack patterns abuse exactly the kind of access update_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Oceanbase, and nothing reaches the server without passing your rules. This is the rule we recommend for update_memory:
{
"version": "1",
"default": "deny",
"tools": {
"update_memory": {
"limits": [
{
"counter": "update_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_memory 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.
Free to start. No card required.
Update memory Args: memory_id: Memory ID content: New content user_id: User identifier agent_id: Agent identifier metadata: Updated metadata Returns: JSON formatted string. It is categorised as a Write tool in the Mcp Oceanbase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for update_memory: 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 Mcp Oceanbase. Nothing to install.
update_memory 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 update_memory 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 update_memory. 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.
update_memory is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.