Measure return loss (S11) at specific frequency
AI agents call vna_measure_return_loss to retrieve information from Copper Mountain Vna without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves measurement data (return loss parameter S11) from the VNA at a specified frequency. It performs no write, destructive, execute, or financial operations—it simply queries and returns measurement results. This is a read-only operation with no side effects or risk of unintended consequences to the instrument or data.
From the tool's definition Tool name 'vna_measure_return_loss' and description 'Measure return loss (S11) at specific frequency' indicate a measurement query operation.
Attacks that exploit this kind of access
Measure return loss (S11) at specific frequency. It is categorised as a Read tool in the Copper Mountain Vna MCP Server, which means it retrieves data without modifying state.
Register the Copper Mountain Vna MCP server in PolicyLayer and add a rule for vna_measure_return_loss: 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_measure_return_loss 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 vna_measure_return_loss 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_measure_return_loss. 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_measure_return_loss 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 →