Get the current custom categories for the project.
AI agents call mem0_get_categories to retrieve information from Mem0 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing category configuration data without creating, modifying, or deleting anything. It is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent—worst case, an agent learns what categories exist but cannot act upon that information destructively.
From the tool's definition Tool name 'mem0_get_categories' and description 'Get the current custom categories for the project' indicate a retrieval operation with no side effects. The verb 'Get' and lack of modification language confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access mem0_get_categories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mem0 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mem0_get_categories:
{
"version": "1",
"default": "deny",
"tools": {
"mem0_get_categories": {}
}
}mem0_get_categories 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 the current custom categories for the project. It is categorised as a Read tool in the Mem0 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mem0 MCP Server MCP server in PolicyLayer and add a rule for mem0_get_categories: 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 Mem0 MCP Server. Nothing to install.
mem0_get_categories 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 mem0_get_categories 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 mem0_get_categories. 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.
mem0_get_categories is provided by the Mem0 MCP Server MCP server (ryaker/mcp-mem0-general). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mem0 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Mem0 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.