create_entity · SQLite Project Memory MCP: Risk & Policy

WHAT IT DOES

What create_entity does on SQLite Project Memory MCP

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

This tool creates new records in the project memory database, making it a Write operation (reversible data creation). It is not Read because it modifies state; not Destructive because creation can be undone (via delete_entity); not Execute because it doesn't run arbitrary code; not Financial because no money is involved.

From the tool's definition Tool description states it 'Create[s] a new authoritative project entity' in a SQLite database. The verb 'create' and context of adding new records to a centralized database indicates data modification without deletion or financial impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_entity Rate-limited

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

What does the create_entity tool do? +

Create a new authoritative project 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 create_entity? +

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

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

Can I rate-limit create_entity? +

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

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

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.