configure_acquisition · Siglent Sds MCP: Risk & Policy

WHAT IT DOES

What configure_acquisition does on Siglent Sds

AI agents invoke configure_acquisition to trigger actions in Siglent Sds. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why configure_acquisition needs a policy

This tool triggers external operations on physical lab equipment (oscilloscope), changing its acquisition state and hardware configuration. It goes beyond mere data writes as it controls real-world instrument behavior. No data is deleted, no money is moved, but it executes commands that alter the operational state of connected hardware.

From the tool's definition 'Control acquisition state and configure timebase/trigger settings' — actively controls hardware state and configures operational parameters of an oscilloscope

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configure_acquisition Rate-limited

configure_acquisition stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "configure_acquisition": {
      "limits": [
        {
          "counter": "configure_acquisition_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Siglent Sds, so you can run agents against it safely.

FAQ

Questions about configure_acquisition

What does the configure_acquisition tool do? +

Control acquisition state and configure timebase/trigger settings. Use. It is categorised as a Execute tool in the Siglent Sds MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on configure_acquisition? +

Register the Siglent Sds MCP server in PolicyLayer and add a rule for configure_acquisition: 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.

What risk level is configure_acquisition? +

configure_acquisition is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit configure_acquisition? +

Yes. Add a rate_limit block to the configure_acquisition 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.

How do I block configure_acquisition completely? +

Set action: deny in the PolicyLayer policy for configure_acquisition. 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.

What MCP server provides configure_acquisition? +

configure_acquisition 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.