upsert_entity · SQLite Project Memory MCP: Risk & Policy

WHAT IT DOES

What upsert_entity does on SQLite Project Memory MCP

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

Upsert operations create or modify data reversibly; they do not execute arbitrary code, delete data irreversibly, or move money. The severity is high rather than medium because this tool modifies the authoritative source of truth for project state, and agents could corrupt project metadata, tasks, or relationships if misused.

From the tool's definition Tool description states 'Create an entity if missing or merge updates into an existing entity.' This performs both creation (write operation) and modification (update) of data in the SQLite database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upsert_entity Rate-limited

upsert_entity 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": {
    "upsert_entity": {
      "limits": [
        {
          "counter": "upsert_entity_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 upsert_entity

What does the upsert_entity tool do? +

Create an entity if missing or merge updates into an existing entity. 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 upsert_entity? +

Register the SQLite Project Memory MCP server in PolicyLayer and add a rule for upsert_entity: 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 upsert_entity? +

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

Can I rate-limit upsert_entity? +

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

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

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