AI agents use add_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 'add_memory' tool appears to create or persist data (memory records) based on its name and context within a database/storage server. This is a Write operation—data is created or modified but not irreversibly deleted. Empty description reduces confidence slightly, but the naming convention and server context support Write classification.
From the tool's definition Tool name 'add_memory' indicates creation/modification of data. Description is empty, limiting confidence. Sibling tools like 'add_data_to_collection' and 'add_memory_with_profile' on the mcp-oceanbase server suggest this adds or stores data reversibly.
Documented attack patterns abuse exactly the kind of access add_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 add_memory:
{
"version": "1",
"default": "deny",
"tools": {
"add_memory": {
"limits": [
{
"counter": "add_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
add_memory. 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 add_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.
add_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 add_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 add_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.
add_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.