Get Redis server information
AI agents call redis_info to retrieve information from Multi-Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and status information from Redis (e.g., memory usage, connected clients, uptime, replication status) with no side effects. It is a pure query operation that does not create, modify, delete, or execute code. The low severity reflects that misuse would only expose non-sensitive operational information, with minimal blast radius.
From the tool's definition Tool name 'redis_info' and description 'Get Redis server information' indicate a read-only operation that retrieves diagnostic/status data from a Redis server without modifying any data.
Attacks that exploit this kind of access
Get Redis server information. It is categorised as a Read tool in the Multi-Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for redis_info: 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 Multi-Database MCP Server. Nothing to install.
redis_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the redis_info 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 redis_info. 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.
redis_info is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →