redis-ping

Tests Redis connectivity by sending a PING command.

SERVERBuild SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What redis-ping does on Build

AI agents invoke redis-ping to trigger actions in Build. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why redis-ping is rated High

This tool actively sends a network command (PING) to a Redis instance, triggering an external operation. While it is read-only and non-destructive in nature, it executes an operation against an external service rather than merely reading local data. Misuse risk is low since PING has no side effects, but it falls under Execute due to the external operation invocation.

From the tool's definition Tests Redis connectivity by sending a PING command

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs redis-ping safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For redis-ping, this is the rule to start with:

redis-ping Rate-limited

redis-ping stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "redis-ping": {
      "limits": [
        {
          "counter": "redis-ping_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about redis-ping

What does the redis-ping tool do? +

Tests Redis connectivity by sending a PING command. It is categorised as a Execute tool in the Build MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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

Register the Build MCP server in PolicyLayer and add a rule for redis-ping: 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 Build. Nothing to install.

What risk level is redis-ping? +

redis-ping is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit redis-ping? +

Yes. Add a rate_limit block to the redis-ping 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-ping completely? +

Set action: deny in the PolicyLayer policy for redis-ping. 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-ping? +

redis-ping is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →