[Controllers] Set application on a controller.
AI agents use controllers_set_app to create or update resources in CyPerf MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CyPerf MCP Server environment.
This tool modifies controller state by setting or updating an application configuration. It is a Write operation because it creates or modifies data (application settings on a controller) in a reversible manner. It is not Destructive (changes are not irreversible), not Execute (it is not running arbitrary code or triggering dynamic operations), and not Read (it modifies rather than retrieves data).
From the tool's definition Tool name 'controllers_set_app' and description 'Set application on a controller' indicate modification of controller configuration/state.
Attacks that exploit this kind of access
[Controllers] Set application on a controller. It is categorised as a Write tool in the CyPerf MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for controllers_set_app: 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_set_app is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the controllers_set_app 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_set_app. 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_set_app 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 →