database_switch · Personal Neo4j Memory Server MCP

WHAT IT DOES

What database_switch does on Personal Neo4j Memory Server

AI agents use database_switch to create or update resources in Personal Neo4j Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Personal Neo4j Memory Server environment.

WHY IT NEEDS A POLICY

Why database_switch needs a policy

With an empty description, I must infer from the tool name. 'database_switch' likely changes the active database context for subsequent operations — a configuration/state change that is reversible (you can switch back), placing it in the Write category. It does not appear to delete data, execute code, or involve finances. Confidence is low due to the empty description.

From the tool's definition Tool name 'database_switch' and empty description. Sibling tools suggest a Neo4j memory management server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

database_switch Rate-limited

database_switch 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": {
    "database_switch": {
      "limits": [
        {
          "counter": "database_switch_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 Personal Neo4j Memory Server, so you can run agents against it safely.

FAQ

Questions about database_switch

What does the database_switch tool do? +

database_switch. It is categorised as a Write tool in the Personal Neo4j Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on database_switch? +

Register the Personal Neo4j Memory Server MCP server in PolicyLayer and add a rule for database_switch: 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 Personal Neo4j Memory Server. Nothing to install.

What risk level is database_switch? +

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

Can I rate-limit database_switch? +

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

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

database_switch is provided by the Personal Neo4j Memory Server MCP server (jeelidev/personal-neo4j-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.