Get specific memory Args: memory_id: Memory ID user_id: User identifier agent_id: Agent identifier Returns: JSON formatted string, returns error message if not found
AI agents call get_memory_by_id to retrieve information from Mcp Oceanbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored memory data by ID without side effects. The operation is read-only, analogous to a database SELECT query. The severity is low because retrieving memory records poses minimal risk even if misused—it cannot modify, delete, or execute code. Confidence is high due to clear retrieval semantics and the straightforward nature of lookup operations.
From the tool's definition Tool name 'get_memory_by_id' and description 'Get specific memory' indicate a retrieval operation. The parameters are identifiers (memory_id, user_id, agent_id) used for lookup, and the return value is 'JSON formatted string' with error handling for not-found…
Documented attack patterns abuse exactly the kind of access get_memory_by_id 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 get_memory_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_memory_by_id": {}
}
}get_memory_by_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get specific memory Args: memory_id: Memory ID user_id: User identifier agent_id: Agent identifier Returns: JSON formatted string, returns error message if not found. It is categorised as a Read tool in the Mcp Oceanbase MCP Server, which means it retrieves data without modifying state.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for get_memory_by_id: 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.
get_memory_by_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_memory_by_id 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 get_memory_by_id. 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.
get_memory_by_id 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.