Get the current acquisition state including sample rate, memory depth, timebase, trigger configuration, and acquisition status.
AI agents call get_acquisition_status 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 is fundamentally a Read operation - it retrieves and queries current oscilloscope acquisition configuration and status without creating, modifying, or deleting data.
From the tool's definition Tool description states it 'Get[s] the current acquisition state' - a retrieval operation with no modification capabilities. However, it queries live oscilloscope state that could reveal sensitive measurement data being captured.
Attacks that exploit this kind of access
Get the current acquisition state including sample rate, memory depth, timebase, trigger configuration, and acquisition status. 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 get_acquisition_status: 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.
get_acquisition_status 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 get_acquisition_status 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 get_acquisition_status. 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.
get_acquisition_status 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 →