Query the oscilloscope identification (*IDN?). Returns manufacturer, model, serial number, and firmware version.
AI agents call identify to retrieve information from Siglent Sds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple query operation using the SCPI *IDN? command to retrieve oscilloscope identification information. It has no ability to modify settings, execute arbitrary commands, delete data, or cause other side effects. The information returned is static metadata about the device itself, making this a pure read operation with minimal risk.
From the tool's definition Tool name 'identify' and description 'Query the oscilloscope identification (*IDN?)' indicate a read-only operation that retrieves device metadata (manufacturer, model, serial number, firmware version) with no modification or side effects.
Attacks that exploit this kind of access
Query the oscilloscope identification (*IDN?). Returns manufacturer, model, serial number, and firmware version. It is categorised as a Read tool in the Siglent Sds MCP Server, which means it retrieves data without modifying state.
Register the Siglent Sds MCP server in PolicyLayer and add a rule for identify: 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 Siglent Sds. Nothing to install.
identify 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 identify 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 identify. 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.
identify is provided by the Siglent Sds MCP server (magnusjohansson/siglent-sds-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 →