gateway_iperf
Run an iperf throughput test from an Aruba gateway (async, polls ~60s).
This record as markdown: /tools/secure-ssid-centralmcp/gateway-iperf.md
What gateway_iperf does on API-Central
AI agents invoke gateway_iperf to trigger actions in API-Central. 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 gateway_iperf is rated High
This tool executes an external operation (iperf test) on network infrastructure whose effects depend on test parameters and gateway state. While not destructive or financial, it triggers an active network operation with real resource implications, making it Execute rather than Read.
From the tool's definition Tool description states 'Run an iperf throughput test' — a direct execution of a network diagnostic command on gateway infrastructure with side effects (network load, resource consumption) that persist for ~60 seconds.
Attacks that exploit this kind of access
The rule that runs gateway_iperf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gateway_iperf, this is the rule to start with:
gateway_iperf 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 API-Central, apply this rule, and every gateway_iperf call is checked against it from then on.
Questions about gateway_iperf
Run an iperf throughput test from an Aruba gateway (async, polls ~60s). It is categorised as a Execute tool in the API-Central MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the API-Central MCP server in PolicyLayer and add a rule for gateway_iperf: 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 API-Central. Nothing to install.
gateway_iperf 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 gateway_iperf 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 gateway_iperf. 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.
gateway_iperf is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
Across the catalogue