memvid_doctor · Memvid MCP: Risk & Policy

WHAT IT DOES

What memvid_doctor does on Memvid

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

WHY IT NEEDS A POLICY

Why memvid_doctor needs a policy

This tool modifies memory files by rebuilding indexes (time, lexical, vector). The 'dry_run' option implies that without it, changes are actually applied, making this a Write operation. It's not Destructive because rebuilding indexes is reversible and restorative rather than deleting data. Severity is medium because misuse could corrupt memory file indexes or cause unintended rewrites.

From the tool's definition Diagnose and repair a memory file... rebuild corrupted indexes... dry_run: Preview changes without applying

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memvid_doctor Rate-limited

memvid_doctor 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": {
    "memvid_doctor": {
      "limits": [
        {
          "counter": "memvid_doctor_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 Memvid, so you can run agents against it safely.

FAQ

Questions about memvid_doctor

What does the memvid_doctor tool do? +

Diagnose and repair a memory file. Can rebuild corrupted indexes: - Time index: chronological ordering - Lexical index: full-text search (Tantivy) - Vector index: similarity search Args: file: Path to the .mv2 memory file rebuild_time_index: Rebuild temporal index rebuild_lex_index: Rebuild full-text search index rebuild_vec_index: Rebuild vector similarity index dry_run: Preview changes without applying Returns: JSON with diagnosis results and repairs performed. It is categorised as a Write tool in the Memvid MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memvid_doctor? +

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

What risk level is memvid_doctor? +

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

Can I rate-limit memvid_doctor? +

Yes. Add a rate_limit block to the memvid_doctor 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 memvid_doctor completely? +

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

memvid_doctor is provided by the Memvid MCP server (tapiocapioca/memvid-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.