Measure calibration standard (OPEN/SHORT/LOAD/THRU)
AI agents invoke vna_calibration_measure_standard to trigger actions in Copper Mountain Vna. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an active measurement operation on physical VNA hardware — it instructs the instrument to perform a calibration standard measurement sweep. This is an external operation that depends on arguments (which standard to measure) and has real-world side effects on the instrument's calibration state.
From the tool's definition Measure calibration standard (OPEN/SHORT/LOAD/THRU)
Attacks that exploit this kind of access
Measure calibration standard (OPEN/SHORT/LOAD/THRU). It is categorised as a Execute tool in the Copper Mountain Vna MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Copper Mountain Vna MCP server in PolicyLayer and add a rule for vna_calibration_measure_standard: 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 Copper Mountain Vna. Nothing to install.
vna_calibration_measure_standard is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vna_calibration_measure_standard 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 vna_calibration_measure_standard. 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.
vna_calibration_measure_standard is provided by the Copper Mountain Vna MCP server (rfingadam/copper-mountain-vna-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 →