run_speed_test · API-Central MCP: Risk & Policy

WHAT IT DOES

What run_speed_test does on API-Central

AI agents invoke run_speed_test 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 IT NEEDS A POLICY

Why run_speed_test needs a policy

This tool executes an operation (speed test) on network infrastructure that has real-world effects: it consumes bandwidth, generates network traffic, and produces results dependent on runtime conditions. While not destructive or financial, it's an active execution of a network diagnostic command rather than a passive read.

From the tool's definition Tool description states it will 'Run a speed test from an AP' — this actively triggers an external network operation whose effects depend on which AP is targeted and when the test runs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_speed_test Rate-limited

run_speed_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": {
    "run_speed_test": {
      "limits": [
        {
          "counter": "run_speed_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches API-Central, so you can run agents against it safely.

FAQ

Questions about run_speed_test

What does the run_speed_test tool do? +

Run a speed test from an AP to measure uplink bandwidth. 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.

How do I enforce a policy on run_speed_test? +

Register the API-Central MCP server in PolicyLayer and add a rule for run_speed_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 API-Central. Nothing to install.

What risk level is run_speed_test? +

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

Can I rate-limit run_speed_test? +

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

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

run_speed_test 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.