save_database · Re MCP: Risk & Policy

WHAT IT DOES

What save_database does on Re

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

WHY IT NEEDS A POLICY

Why save_database needs a policy

The tool creates or overwrites a database file on disk. While the operation itself is reversible (can be undone by restoring from backup or reloading a prior version), it commits in-memory changes to persistent storage.

From the tool's definition save_database saves/persists the current database to disk, a reversible write operation that modifies stored data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_database Rate-limited

save_database 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_database": {
      "limits": [
        {
          "counter": "save_database_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 Re, so you can run agents against it safely.

FAQ

Questions about save_database

What does the save_database tool do? +

Save the current database to disk (may take minutes for large DBs). It is categorised as a Write tool in the Re 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_database? +

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

What risk level is save_database? +

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

Can I rate-limit save_database? +

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

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

save_database is provided by the Re MCP server (jtsylve/re-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.