ping_test

执行 Ping 测试

SERVERIkuai SOURCEgxxHuang/ikuai-mcp-server

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/ikuai-mcp-server/ping-test.md

WHAT IT DOES

What ping_test does on Ikuai

AI agents invoke ping_test to trigger actions in Ikuai. 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 ping_test is rated High

This tool actively sends ICMP packets to external hosts, constituting an external network operation. It falls under Execute as it triggers real network activity. Misuse could be used for network reconnaissance or to probe internal/external hosts from the router's vantage point, giving it a medium severity.

From the tool's definition 执行 Ping 测试 — '执行' means 'execute', and Ping test triggers external network operations

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ping_test safely

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

ping_test Rate-limited

ping_test 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": {
    "ping_test": {
      "limits": [
        {
          "counter": "ping_test_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 Ikuai, apply this rule, and every ping_test call is checked against it from then on.

FAQ

Questions about ping_test

What does the ping_test tool do? +

执行 Ping 测试. It is categorised as a Execute tool in the Ikuai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ping_test? +

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

What risk level is ping_test? +

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

Can I rate-limit ping_test? +

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

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

ping_test is provided by the Ikuai MCP server (gxxHuang/ikuai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ikuai, and thousands of servers like it.

This server

All 229 Ikuai tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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