Get all current settings for a channel in one call.
AI agents call scope_channel_info to retrieve information from LeCroy Oscilloscope MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state/configuration of an oscilloscope channel and returns information. It performs no modifications, deletions, code execution, or financial operations. The read-only nature of retrieving settings makes it the least risky category. Low severity is appropriate as misuse would only expose instrument configuration data without affecting measurement capability or causing harm.
From the tool's definition Tool description states 'Get all current settings for a channel' - retrieves configuration data without modification or side effects. Name 'scope_channel_info' and verb 'Get' indicate a query operation.
Attacks that exploit this kind of access
Get all current settings for a channel in one call. It is categorised as a Read tool in the LeCroy Oscilloscope MCP MCP Server, which means it retrieves data without modifying state.
Register the LeCroy Oscilloscope MCP server in PolicyLayer and add a rule for scope_channel_info: 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 LeCroy Oscilloscope MCP. Nothing to install.
scope_channel_info 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 scope_channel_info 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 scope_channel_info. 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.
scope_channel_info is provided by the LeCroy Oscilloscope MCP server (lucasgerads/lecroy-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 →