redis-info
Gets Redis server info with structured sections (server, clients, memory, etc.).
This record as markdown: /tools/io-github-dave-london-npm/redis-info.md
What redis-info does on Npm
AI agents call redis-info to retrieve information from Npm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why redis-info is rated Low
The tool performs an informational query against a Redis server to retrieve diagnostic and operational data. This is a read-only operation with no capability to modify state, execute commands, or cause destructive changes. The structured output (server, clients, memory sections) indicates introspection/monitoring use case.
From the tool's definition Tool description states 'Gets Redis server info' — a retrieval operation that returns server metadata and statistics with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs redis-info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For redis-info, this is the rule to start with:
redis-info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Npm, apply this rule, and every redis-info call is checked against it from then on.
Questions about redis-info
Gets Redis server info with structured sections (server, clients, memory, etc.). It is categorised as a Read tool in the Npm MCP Server, which means it retrieves data without modifying state.
Register the Npm 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 Npm. 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 Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Npm, and thousands of servers like it.
This server
Across the catalogue