set_project_root · SQLite Project Memory MCP: Risk & Policy

WHAT IT DOES

What set_project_root does on SQLite Project Memory MCP

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

This tool changes project-level configuration (root directory, database reference, export path) and re-establishes database connections. While it does not create, delete, or execute arbitrary code, it modifies the operational state of the system in a reversible manner—the previous project context could be restored by calling the tool again with different parameters.

From the tool's definition Tool description states it 'Switch[es] project context (root + db + export path) and reconnect[s] database,' which modifies configuration state and database connections.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_project_root Rate-limited

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

What does the set_project_root tool do? +

Switch project context (root + db + export path) and reconnect database. 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 set_project_root? +

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

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

Can I rate-limit set_project_root? +

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

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

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