AI agents use add_memory_with_profile 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.
This tool appears to create or modify memory records associated with a profile. This is a reversible write operation (the data can be updated or cleared later) rather than a destructive deletion. Without additional context about the scope or side effects, 'medium' severity is appropriate—misuse could corrupt or pollute stored memory/profile data, but is not irreversible or financial in nature.
From the tool's definition Tool name 'add_memory_with_profile' indicates it adds or stores memory data, suggesting a write operation that creates or modifies data. The description is empty, reducing confidence.
Documented attack patterns abuse exactly the kind of access add_memory_with_profile 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_with_profile:
{
"version": "1",
"default": "deny",
"tools": {
"add_memory_with_profile": {
"limits": [
{
"counter": "add_memory_with_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_memory_with_profile 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_with_profile. 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_with_profile: 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_with_profile 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_with_profile 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_with_profile. 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_with_profile 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.