mem0_add · VibeServe MCP: Risk & Policy

WHAT IT DOES

What mem0_add does on VibeServe

AI agents use mem0_add to create or update resources in VibeServe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VibeServe environment.

WHY IT NEEDS A POLICY

Why mem0_add needs a policy

This tool creates or stores new data (a memory entry) in a reversible manner. It does not execute code, delete data, or commit financial transactions. The operation is Write-class because it adds information to a system, and the severity is low because storing a memory has limited blast radius unless the memory system is used for critical authentication or security decisions, which is not indicated here.

From the tool's definition Tool name 'mem0_add' and description 'Store a memory in mem0' indicate a create operation that adds data to a memory system without deleting or modifying existing records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mem0_add Rate-limited

mem0_add 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mem0_add": {
      "limits": [
        {
          "counter": "mem0_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches VibeServe, so you can run agents against it safely.

FAQ

Questions about mem0_add

What does the mem0_add tool do? +

Store a memory in mem0. It is categorised as a Write tool in the VibeServe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mem0_add? +

Register the VibeServe MCP server in PolicyLayer and add a rule for mem0_add: 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 VibeServe. Nothing to install.

What risk level is mem0_add? +

mem0_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mem0_add? +

Yes. Add a rate_limit block to the mem0_add 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.

How do I block mem0_add completely? +

Set action: deny in the PolicyLayer policy for mem0_add. 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.

What MCP server provides mem0_add? +

mem0_add is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.