27 tools from the Betterdb MCP Server, categorised by risk level.
View the Betterdb policy →get_acl_audit Get persisted ACL audit log entries from storage. Filter by username, reason (auth, command, key, channel), or time range. Use this to investigate ... get_anomalies Get anomaly detection events from persisted storage. BetterDB continuously runs Z-score analysis on memory, hit rate, CPU, and other metrics — this... get_client_activity Get time-bucketed client activity from persisted snapshots. Shows connection counts, command distribution, and buffer usage over time. Use startTim... get_clients Get the active client list with connection details. get_cluster_node_stats Get per-node performance stats: memory usage, ops/sec, connected clients, replication offset, and CPU. Use this to identify hot nodes, lagging repl... get_cluster_nodes Discover all nodes in the Valkey cluster — role (master/replica), address, health status, and slot ranges. Returns an error message if this instanc... get_cluster_slowlog Get the aggregated slowlog across ALL nodes in the cluster. This is the primary tool for finding slow commands in cluster mode — per-node slowlogs ... get_commandlog Get the most recent entries from COMMANDLOG (Valkey 8+ only, superset of slowlog). get_commandlog_history Get persisted COMMANDLOG entries from storage (Valkey 8+ only). Supports time range filtering to investigate specific incidents. Returns empty with... 2/5 get_commandlog_patterns Get analyzed COMMANDLOG patterns from persisted storage (Valkey 8+ only). Like get_slowlog_patterns but includes large-request and large-reply patt... get_health Get a synthetic health summary for the active instance: keyspace hit rate, memory fragmentation ratio, connected clients, replication lag (replicas... get_hot_keys Get hot key tracking data from persisted storage. BetterDB periodically scans keys using LFU frequency scores (when maxmemory-policy is an LFU vari... get_info Get INFO stats for the active instance. Contains all health data: memory, clients, replication, keyspace, stats (hit rate, ops/sec), and server inf... get_latency Get latency event history for the active instance. get_latency_history Get the full latency history for a named event (e.g. 'command', 'fast-command'). Call get_latency first to see which event names are available, the... get_memory Get memory diagnostics: MEMORY DOCTOR assessment and MEMORY STATS breakdown. get_slot_stats Get per-slot key counts and CPU usage (Valkey 8.0+ only). Use orderBy='cpu-usec' to find hot slots, or 'key-count' to find the most populated slots... get_slowlog Get the most recent slow commands from the slowlog. get_slowlog_patterns Get analyzed slowlog patterns from persisted storage. Groups slow commands by normalized pattern, showing frequency, average duration, and example ... list_instances List all Valkey/Redis instances registered in BetterDB. Shows connection status and capabilities. test_connection Test a Valkey/Redis connection without persisting it. Use before add_connection to validate credentials. 2/5 start_monitor Start the BetterDB monitor as a persistent background process. If already running, returns the existing URL. The monitor persists across MCP sessio... 3/5 stop_monitor Stop a persistent BetterDB monitor process that was previously started with start_monitor or --autostart --persist. 3/5 The Betterdb MCP server exposes 27 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Betterdb server.
Betterdb tools are categorised as Read (21), Write (3), Destructive (1), Execute (2). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept