memvid_unlock · Memvid MCP: Risk & Policy

WHAT IT DOES

What memvid_unlock does on Memvid

AI agents use memvid_unlock 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_unlock needs a policy

While decryption itself is a read operation, the tool's primary function is to write the decrypted result to disk. This crosses into Write territory because it creates new file data at the output path. The severity is medium because misuse could expose sensitive encrypted data if an attacker gains access to decrypt credentials or if an AI agent decrypts files without proper authorization.

From the tool's definition Decrypts an encrypted memory file from .mv2e format to .mv2 format and writes the decrypted output to a specified path. The tool creates/modifies data by producing a new decrypted file.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memvid_unlock Rate-limited

memvid_unlock 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_unlock": {
      "limits": [
        {
          "counter": "memvid_unlock_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_unlock

What does the memvid_unlock tool do? +

Decrypt an encrypted memory file. Decrypts a .mv2e file back to .mv2 format. Args: file: Path to the encrypted .mv2e file output: Output path for the decrypted file (.mv2) password: Decryption password (required for non-interactive use) Returns: {. 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_unlock? +

Register the Memvid MCP server in PolicyLayer and add a rule for memvid_unlock: 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_unlock? +

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

Can I rate-limit memvid_unlock? +

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

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

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