Get all current trigger settings in one call.
AI agents call scope_trigger_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 only retrieves/queries the current trigger settings from the oscilloscope without modifying any state or causing side effects. It is a pure read operation.
From the tool's definition Get all current trigger settings in one call
Attacks that exploit this kind of access
Get all current trigger settings 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_trigger_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_trigger_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_trigger_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_trigger_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_trigger_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 →