Batch add multiple files from a directory with progress tracking. Optimized for large directories with commit batching. Args: file: Path to the .mv2 memory file input: Path to input directory recursive: Include subdirectories parallel: Process files in parallel batch_size: Number of files per com...
AI agents use memvid_put_many 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.
memvid_put_many creates or inserts multiple file entries into a .mv2 memory file in batches. This is a reversible write operation (data can be corrected or deleted via sibling tools like memvid_correct or memvid_delete). The severity is medium because bulk insertion of files could consume storage or memory resources, and mistakes could require cleanup, but the operation itself is not destructive or financial.
From the tool's definition Tool description states "Batch add multiple files from a directory" — the word "add" indicates creation/insertion of data into the memory file. Arguments include file path and batch processing parameters for commits, confirming data modification.
Attacks that exploit this kind of access
Batch add multiple files from a directory with progress tracking. Optimized for large directories with commit batching. Args: file: Path to the .mv2 memory file input: Path to input directory recursive: Include subdirectories parallel: Process files in parallel batch_size: Number of files per commit batch (default: 100) Returns: JSON with batch processing statistics. 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.
Register the Memvid MCP server in PolicyLayer and add a rule for memvid_put_many: 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.
memvid_put_many is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the memvid_put_many 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 memvid_put_many. 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.
memvid_put_many 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →