controllers_nodes
AI agents call controllers_nodes 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.
With no description, classification relies on the tool name and server context. 'controllers_nodes' most likely retrieves or lists controller node information for network performance testing orchestration, consistent with Read-category tools that query system state without modification.
From the tool's definition Tool name 'controllers_nodes' suggests querying or listing controller nodes. No description provided. Context shows it is among sibling tools like 'agents_list', 'agents_get' which are Read operations, and the server's stated purpose includes 'manage agents'…
Attacks that exploit this kind of access
controllers_nodes. 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_nodes: 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_nodes 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_nodes 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_nodes. 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_nodes 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 →