BETTERDB TOOLS

41 tools from the Betterdb MCP Server, categorised by risk level.

READ 32 tools
Read cache_get_proposal Fetch a single cache proposal by id, including its audit trail. Read cache_health Detailed health for a single cache. Response branches by type: semantic_cache reports category_breakdown + ... Read cache_list List all caches (semantic_cache and agent_cache) registered for the active instance, with hit rate and tota... Read cache_list_pending_proposals List pending cache proposals for the active instance, newest first. Optionally filter by cache_name. Read cache_propose_invalidate Propose a cache invalidation for review. Filter shape depends on cache type: semantic_cache requires filter... Read cache_propose_threshold_adjust Propose a semantic-cache similarity-threshold change for review. Creates a pending proposal that requires h... Read cache_propose_tool_ttl_adjust Propose an agent-cache per-tool TTL change for review. Creates a pending proposal that requires human appro... Read cache_recent_changes Recent proposals for a single cache (any status), so agents can avoid re-proposing pending or recently-appl... Read cache_similarity_distribution Histogram of recent similarity scores (20 buckets, width 0.1) for a semantic_cache. Errors on agent_cache. Read cache_threshold_recommendation Threshold-tuning recommendation for a semantic_cache, based on the rolling similarity-score window. Errors ... Read cache_tool_effectiveness Per-tool hit rate, cost saved, and TTL recommendation for an agent_cache. Errors with INVALID_CACHE_TYPE on... Read get_acl_audit Get persisted ACL audit log entries from storage. Filter by username, reason (auth, command, key, channel),... Read get_anomalies Get anomaly detection events from persisted storage. BetterDB continuously runs Z-score analysis on memory,... Read get_client_activity Get time-bucketed client activity from persisted snapshots. Shows connection counts, command distribution, ... Read get_clients Get the active client list with connection details. Read get_cluster_node_stats Get per-node performance stats: memory usage, ops/sec, connected clients, replication offset, and CPU. Use ... Read get_cluster_nodes Discover all nodes in the Valkey cluster — role (master/replica), address, health status, and slot ranges. ... Read get_cluster_slowlog Get the aggregated slowlog across ALL nodes in the cluster. This is the primary tool for finding slow comma... Read get_commandlog Get the most recent entries from COMMANDLOG (Valkey 8+ only, superset of slowlog). Read get_commandlog_history Get persisted COMMANDLOG entries from storage (Valkey 8+ only). Supports time range filtering to investigat... Read get_commandlog_patterns Get analyzed COMMANDLOG patterns from persisted storage (Valkey 8+ only). Like get_slowlog_patterns but inc... Read get_health Get a synthetic health summary for the active instance: keyspace hit rate, memory fragmentation ratio, conn... Read get_hot_keys Get hot key tracking data from persisted storage. BetterDB periodically scans keys using LFU frequency scor... Read get_info Get INFO stats for the active instance. Contains all health data: memory, clients, replication, keyspace, s... Read get_latency Get latency event history for the active instance. Read get_latency_history Get the full latency history for a named event (e.g. 'command', 'fast-command'). Call get_latency first to ... Read get_memory Get memory diagnostics: MEMORY DOCTOR assessment and MEMORY STATS breakdown. Read 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... Read get_slowlog Get the most recent slow commands from the slowlog. Read get_slowlog_patterns Get analyzed slowlog patterns from persisted storage. Groups slow commands by normalized pattern, showing f... Read list_instances List all Valkey/Redis instances registered in BetterDB. Shows connection status and capabilities. Read test_connection Test a Valkey/Redis connection without persisting it. Use before add_connection to validate credentials.

The managed route: connect Betterdb through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @betterdb/mcp
How many tools does the Betterdb MCP server have? +

The Betterdb MCP server exposes 41 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Betterdb tools? +

Route the Betterdb server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Betterdb tools fall into? +

Betterdb tools are categorised as Read (32), Write (6), Destructive (1), Execute (2). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.