Set the cursor type.
AI agents use scope_set_cursor_type to create or update resources in LeCroy Oscilloscope MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LeCroy Oscilloscope MCP environment.
This tool modifies oscilloscope settings (cursor type) which affects the display state reversibly. It does not read data permanently, execute external code, destroy data, or involve financial transactions. It is a Write operation because it configures a parameter that can be undone by setting it to a different value.
From the tool's definition The tool 'scope_set_cursor_type' sets (modifies) the cursor type on a LeCroy oscilloscope. This is a configuration change to the oscilloscope's display/interface state. The description explicitly uses 'Set', indicating a write operation.
Attacks that exploit this kind of access
Set the cursor type. It is categorised as a Write tool in the LeCroy Oscilloscope MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LeCroy Oscilloscope MCP server in PolicyLayer and add a rule for scope_set_cursor_type: 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_set_cursor_type 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 scope_set_cursor_type 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_set_cursor_type. 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_set_cursor_type 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 →