save_all_buffers · Vigentic MCP: Risk & Policy

WHAT IT DOES

What save_all_buffers does on Vigentic MCP

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

WHY IT NEEDS A POLICY

Why save_all_buffers needs a policy

This tool creates or modifies data on the filesystem by persisting buffer contents to disk. While file modifications are reversible (can be undone by editing or version control), the tool's purpose is to commit changes to the file system. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).

From the tool's definition Tool is named 'save_all_buffers' and description states it will 'Save every dirty file-backed open buffer'. The action of saving modifies files on disk, which is a write operation that persists changes reversibly.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_all_buffers Rate-limited

save_all_buffers 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": {
    "save_all_buffers": {
      "limits": [
        {
          "counter": "save_all_buffers_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 Vigentic MCP, so you can run agents against it safely.

FAQ

Questions about save_all_buffers

What does the save_all_buffers tool do? +

Save every dirty file-backed open buffer and report saved, skipped, and failed entries. It is categorised as a Write tool in the Vigentic MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_all_buffers? +

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

What risk level is save_all_buffers? +

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

Can I rate-limit save_all_buffers? +

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

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

save_all_buffers is provided by the Vigentic MCP server (munozu/vigentic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.