sessions_set_network_ip_range
AI agents use sessions_set_network_ip_range 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.
The name suggests this tool modifies (sets/writes) an IP range configuration for a network session. 'Set' operations are typically reversible writes. Empty description lowers confidence significantly. Severity is medium as misconfiguring network IP ranges could disrupt testing but is generally reversible.
From the tool's definition Tool name 'sessions_set_network_ip_range' — 'set' implies modification of a network IP range configuration within a session.
Attacks that exploit this kind of access
sessions_set_network_ip_range. 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.
Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for sessions_set_network_ip_range: 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.
sessions_set_network_ip_range is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sessions_set_network_ip_range 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.
Set action: deny in the PolicyLayer policy for sessions_set_network_ip_range. 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.
sessions_set_network_ip_range 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →