sessions_get_config
AI agents call sessions_get_config to retrieve information from CyPerf MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration information about sessions without modifying, executing, or deleting anything. The 'get' operation is inherently a Read action with no side effects. In the context of a network testing platform, retrieving session config is a standard query operation. Low severity because it only accesses existing data without actionable external effects.
From the tool's definition Tool name 'sessions_get_config' clearly indicates retrieval of session configuration data. The 'get' verb is a hallmark of Read operations. No description provided, but the name structure is unambiguous.
Attacks that exploit this kind of access
sessions_get_config. It is categorised as a Read tool in the CyPerf MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for sessions_get_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_get_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sessions_get_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_get_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_get_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 →