redis-info

Gets Redis server info with structured sections (server, clients, memory, etc.).

SERVERGithub SOURCE@paretools/github

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-github/redis-info.md

WHAT IT DOES

What redis-info does on Github

AI agents call redis-info to retrieve information from Github without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why redis-info is rated Low

The tool retrieves and reports structured server information (server, clients, memory, etc.) with no side effects, data modification, or code execution capability. This is a standard informational/diagnostic query operation with minimal risk if misused by an AI agent.

From the tool's definition Tool name 'redis-info' and description 'Gets Redis server info' indicate a read-only query operation that retrieves diagnostic information about a Redis server without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs redis-info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Github, 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 Allowed

redis-info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "redis-info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every redis-info call is checked against it from then on.

FAQ

Questions about redis-info

What does the redis-info tool do? +

Gets Redis server info with structured sections (server, clients, memory, etc.). It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on redis-info? +

Register the Github 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 Github. Nothing to install.

What risk level is redis-info? +

redis-info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit redis-info? +

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.

How do I block redis-info completely? +

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.

What MCP server provides redis-info? +

redis-info is provided by the Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 202 Github tools →

Across the catalogue

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →