redis-info
Gets Redis server info with structured sections (server, clients, memory, etc.).
This record as markdown: /tools/io-github-dave-london-cargo/redis-info.md
What redis-info does on Cargo
AI agents call redis-info to retrieve information from Cargo 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
This tool queries Redis server information and returns structured diagnostic data about the server state, clients, and memory usage. No side effects, modifications, or destructive operations are possible.
From the tool's definition Tool name is 'redis-info' and description states it 'Gets Redis server info with structured sections (server, clients, memory, etc.)'. The verb 'Gets' and absence of any modification language indicate a read-only retrieval operation.
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 Cargo, 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 Cargo, 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 Cargo MCP Server, which means it retrieves data without modifying state.
Register the Cargo 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 Cargo. 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 Cargo 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 Cargo, and thousands of servers like it.
This server
Across the catalogue