controllers_ports
AI agents call controllers_ports 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.
The tool appears designed to retrieve port configuration or status from CyPerf controllers. Without evidence of modification, deletion, execution, or financial impact, and given the passive naming pattern consistent with other 'get'/'list' operations on this server (e.g., agents_list, agents_get), this is classified as a Read operation with low severity and moderate confidence due to empty description.
From the tool's definition Tool name 'controllers_ports' suggests querying or listing port information from controllers. No description provided, but naming convention (noun + plural) and context within a testing/orchestration platform indicates a read/query operation.
Attacks that exploit this kind of access
controllers_ports. 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 controllers_ports: 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.
controllers_ports 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 controllers_ports 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 controllers_ports. 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.
controllers_ports 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 →