test_stop · CyPerf MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_stop does on CyPerf MCP Server

AI agents invoke test_stop 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_stop needs a policy

The name strongly implies stopping a running test, which is an external operation with real effects on test execution. Since the description is empty, confidence is reduced, but stopping an active test is an irreversible action in the moment (cannot un-stop a test run) and has significant impact. It falls best under Execute as it triggers an external operation. Not Destructive as it doesn't delete/overwrite data.

From the tool's definition Tool name 'test_stop' on a server that orchestrates network performance and security tests; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_stop Rate-limited

test_stop 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_stop": {
      "limits": [
        {
          "counter": "test_stop_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_stop

What does the test_stop tool do? +

test_stop. 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_stop? +

Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for test_stop: 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_stop? +

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

Can I rate-limit test_stop? +

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

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

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