[Sessions] Get session metadata.
AI agents call sessions_get_meta 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 session metadata—information about existing sessions—with no side effects or state changes. It follows the Read category pattern of querying or fetching data. The narrow scope (metadata only) and read-only nature result in low severity if misused by an agent, as it cannot affect system state or trigger external operations.
From the tool's definition Tool name 'sessions_get_meta' and description 'Get session metadata' indicate retrieval of metadata without modification. The verb 'Get' and lack of any mutating language (create, delete, modify, execute) clearly indicate a read-only operation.
Attacks that exploit this kind of access
[Sessions] Get session metadata. 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_meta: 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_meta 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_meta 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_meta. 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_meta 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 →