sessions_rename_network_segments · CyPerf MCP Server MCP

WHAT IT DOES

What sessions_rename_network_segments does on CyPerf MCP Server

AI agents use sessions_rename_network_segments to create or update resources in CyPerf MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CyPerf MCP Server environment.

WHY IT NEEDS A POLICY

Why sessions_rename_network_segments needs a policy

Renaming network segments is a reversible write operation that modifies configuration state in an active test session. While not destructive (no data loss) or executable (no code/commands), it alters session structure in ways that could disrupt ongoing tests or cause confusion if renamed incorrectly.

From the tool's definition Tool name contains 'rename' and description states 'Rename network segments in a session' — a clear modification operation that changes metadata of existing resources without deleting them.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sessions_rename_network_segments Rate-limited

sessions_rename_network_segments stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sessions_rename_network_segments": {
      "limits": [
        {
          "counter": "sessions_rename_network_segments_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 sessions_rename_network_segments

What does the sessions_rename_network_segments tool do? +

[Sessions] Rename network segments in a session. It is categorised as a Write tool in the CyPerf MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sessions_rename_network_segments? +

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

sessions_rename_network_segments is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sessions_rename_network_segments? +

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

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

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