sessions_save_config
AI agents use sessions_save_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.
Without an explicit description, confidence is moderately reduced. However, the naming pattern and context of a network testing platform where 'save_config' operations typically persist settings to storage suggest a Write operation. This is reversible (configs can be updated/overwritten) rather than destructive, and does not execute code or move money.
From the tool's definition Tool named 'sessions_save_config' appears to persist or modify session configuration settings. Sibling tools like 'agents_set_dpdk' and 'agents_set_ntp' confirm this server performs configuration changes.
Attacks that exploit this kind of access
sessions_save_config. 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_save_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_save_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_save_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_save_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_save_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.
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 →