create_snapshot · SQLite Project Memory MCP: Risk & Policy

WHAT IT DOES

What create_snapshot does on SQLite Project Memory MCP

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

WHY IT NEEDS A POLICY

Why create_snapshot needs a policy

This tool creates new records (snapshots) in the SQLite database, which is a reversible Write operation. While snapshots are typically immutable once created, the act of creating them constitutes data persistence rather than destruction. The severity is medium because misuse could create many snapshots consuming storage or obscuring actual project state, but this is recoverable via deletion of snapshots.

From the tool's definition The tool creates a named snapshot of current project state. The verb 'create' and action of capturing/storing a snapshot indicates data creation/persistence without deletion or irreversible modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_snapshot Rate-limited

create_snapshot 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": {
    "create_snapshot": {
      "limits": [
        {
          "counter": "create_snapshot_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 SQLite Project Memory MCP, so you can run agents against it safely.

FAQ

Questions about create_snapshot

What does the create_snapshot tool do? +

Create a named snapshot of current project state. It is categorised as a Write tool in the SQLite Project Memory 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 create_snapshot? +

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

What risk level is create_snapshot? +

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

Can I rate-limit create_snapshot? +

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

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

create_snapshot is provided by the SQLite Project Memory MCP server (webrtcgame/sqlite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.