[Controllers] Clear port ownership on a controller.
AI agents call controllers_clear_ports to permanently remove resources in CyPerf MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing port ownership forcibly removes existing assignments on a controller, disrupting active tests or configurations. This is effectively irreversible without manual reconfiguration, making it Destructive. The blast radius is high as it could disrupt network testing operations across multiple ports on a controller.
From the tool's definition 'Clear port ownership on a controller' — clearing ownership is an irreversible reset action that removes port assignments, which cannot be undone without manual reassignment
Attacks that exploit this kind of access
[Controllers] Clear port ownership on a controller. It is categorised as a Destructive tool in the CyPerf MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for controllers_clear_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_clear_ports is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the controllers_clear_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_clear_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_clear_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 →