get_or_create_entity · SQLite Project Memory MCP

WHAT IT DOES

What get_or_create_entity does on SQLite Project Memory MCP

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

The tool conditionally creates a new entity if one does not already exist. The creation path is a Write operation (generating a new record with a stable ID). The reuse path is a Read, but since the most severe applicable category applies and creation is a core behavior, this is classified as Write. Misuse could result in unintended entity creation, polluting the data model.

From the tool's definition 'Reuse an exact entity when it already exists or create one with a generated stable id'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

get_or_create_entity Rate-limited

get_or_create_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": {
    "get_or_create_entity": {
      "limits": [
        {
          "counter": "get_or_create_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 get_or_create_entity

What does the get_or_create_entity tool do? +

Reuse an exact entity when it already exists or create one with a generated stable id. 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 get_or_create_entity? +

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

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

Can I rate-limit get_or_create_entity? +

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

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

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