[Sessions] List actions for an application in a session's traffic profile.
AI agents call sessions_get_app_actions 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 or queries application actions from a traffic profile within a session. It performs no side effects, does not modify data, and does not execute operations. This is a straightforward data retrieval operation fitting the 'Read' category with low severity since it only exposes monitoring/analysis information.
From the tool's definition Tool name includes 'get' and description states 'List actions' - both indicate data retrieval with no modification. The verb 'list' is explicitly a read operation that queries existing session traffic profile data.
Attacks that exploit this kind of access
[Sessions] List actions for an application in a session's traffic profile. 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_app_actions: 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_app_actions 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_app_actions 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_app_actions. 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_app_actions 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 →