archive_entity · SQLite Project Memory MCP: Risk & Policy

WHAT IT DOES

What archive_entity does on SQLite Project Memory MCP

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

Archiving is a state modification operation, placing it in the Write category rather than Destructive. The tool explicitly preserves history and related project memory, confirming reversibility. The severity is medium because archiving could hide important project data from view, potentially disrupting workflows, but the data remains recoverable and the action is not irreversible.

From the tool's definition The tool 'archive_entity' modifies data by changing an entity's state to archived, as indicated by 'Archive an entity' in the description. This is a reversible operation (entities can be unarchived) that does not permanently delete data or its history.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_entity Rate-limited

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

What does the archive_entity tool do? +

Archive an entity without deleting its history or related project memory. 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 archive_entity? +

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

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

Can I rate-limit archive_entity? +

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

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

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