licensing_test_connectivity · CyPerf MCP Server MCP

WHAT IT DOES

What licensing_test_connectivity does on CyPerf MCP Server

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

This tool actively tests connectivity to an external server, which involves triggering a network operation/probe to the license backend. It is not purely a read/query of local data, but an action that initiates an outbound connection attempt. Severity is low as it is a read-only connectivity check with minimal blast radius.

From the tool's definition Test connectivity to the license backend server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

licensing_test_connectivity Rate-limited

licensing_test_connectivity 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": {
    "licensing_test_connectivity": {
      "limits": [
        {
          "counter": "licensing_test_connectivity_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 licensing_test_connectivity

What does the licensing_test_connectivity tool do? +

[Licensing] Test connectivity to the license backend server. 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 licensing_test_connectivity? +

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

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

Can I rate-limit licensing_test_connectivity? +

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

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

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