AI agents use database_switch to create or update resources in Neo4j Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neo4j Memory Server environment.
Based on the name alone, 'database_switch' likely changes the active database or project context within the Neo4j Memory Server. This is most analogous to a Write/configuration-change operation (switching state), though it could also be a Read-like operation. Without a description, confidence is low.
From the tool's definition Tool name 'database_switch' only; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access database_switch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Neo4j Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for database_switch:
{
"version": "1",
"default": "deny",
"tools": {
"database_switch": {
"limits": [
{
"counter": "database_switch_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
database_switch. It is categorised as a Write tool in the Neo4j Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 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 Neo4j Memory Server. Nothing to install.
database_switch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
database_switch is provided by the Neo4j Memory Server MCP server (sylweriusz/mcp-neo4j-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Neo4j Memory Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Neo4j Memory Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.