This record as markdown: /tools/ikuai-mcp-server/iperf-test.md
What iperf_test does on Ikuai
AI agents invoke iperf_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.
Why iperf_test is rated High
This tool executes an iPerf network performance test, which actively initiates network connections and consumes bandwidth. It is an Execute category action as it runs an external/internal network test operation. Misuse could saturate network links or disrupt traffic, hence medium severity.
From the tool's definition 执行 iPerf 吞吐测试 — '执行' means 'execute/run'; iPerf is a network throughput testing tool that actively runs bandwidth tests
Attacks that exploit this kind of access
The rule that runs iperf_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 iperf_test, this is the rule to start with:
iperf_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ikuai, apply this rule, and every iperf_test call is checked against it from then on.
Questions about iperf_test
执行 iPerf 吞吐测试. 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.
Register the Ikuai MCP server in PolicyLayer and add a rule for iperf_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.
iperf_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the iperf_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.
Set action: deny in the PolicyLayer policy for iperf_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.
iperf_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.
More on Ikuai, and thousands of servers like it.
Across the catalogue