upsert_attributes · SQLite Project Memory MCP: Risk & Policy

WHAT IT DOES

What upsert_attributes does on SQLite Project Memory MCP

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

Upsert (create or update) is a Write operation because it modifies entity metadata in a controlled, reversible manner. It ranks below Destructive (no deletion) and Execute (no code execution), but above Read (modifies state).

From the tool's definition Tool name 'upsert_attributes' indicates create-or-update semantics. Description states 'Create or update flexible metadata for an entity.' This is a reversible modification operation that does not irreversibly delete data nor execute arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upsert_attributes Rate-limited

upsert_attributes 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_attributes": {
      "limits": [
        {
          "counter": "upsert_attributes_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_attributes

What does the upsert_attributes tool do? +

Create or update flexible metadata for an 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_attributes? +

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

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

Can I rate-limit upsert_attributes? +

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

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

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