[Sessions] Load a configuration into a session.
AI agents use sessions_load_config 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.
Loading a configuration into a session modifies the session's state by applying a new configuration. This is a reversible write operation — the session can be reconfigured again — with no evidence of irreversible deletion, code execution, or financial impact. Misuse could disrupt active test sessions, hence medium severity.
From the tool's definition Load a configuration into a session
Attacks that exploit this kind of access
[Sessions] Load a configuration into 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.
Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for sessions_load_config: 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_load_config 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_load_config 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_load_config. 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_load_config 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.
sessions_load_config is one line of CyPerf MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →