test_start · CyPerf MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_start does on CyPerf MCP Server

AI agents invoke test_start to trigger actions in CyPerf MCP Server. 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 test_start needs a policy

This tool initiates an active test run on the CyPerf platform, which executes network performance and security tests against real infrastructure. Misuse could generate significant network traffic, consume agent resources, or trigger security test scenarios against unintended targets. It fits Execute as it triggers an external operation whose effects depend on the configured test parameters.

From the tool's definition 'Start a test run for a session. Polls until the test is running.' — triggers an external network performance/security test operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_start Rate-limited

test_start 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": {
    "test_start": {
      "limits": [
        {
          "counter": "test_start_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 CyPerf MCP Server, so you can run agents against it safely.

FAQ

Questions about test_start

What does the test_start tool do? +

[Test Operations] Start a test run for a session. Polls until the test is running. It is categorised as a Execute tool in the CyPerf MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_start? +

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

What risk level is test_start? +

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

Can I rate-limit test_start? +

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

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

test_start is provided by the CyPerf MCP Server MCP server (keysight/cyperf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.