auto_setup · Niscope MCP: Risk & Policy

WHAT IT DOES

What auto_setup does on Niscope

AI agents invoke auto_setup to trigger actions in Niscope. 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 auto_setup needs a policy

This tool triggers an automatic configuration operation on physical hardware (an oscilloscope), which constitutes executing an external operation. It modifies device settings automatically, but is reversible (settings can be reconfigured), placing it in Execute rather than Write since it triggers a hardware action/operation rather than simply writing a data record.

From the tool's definition Auto-configure the oscilloscope (equivalent to pressing [Auto Setup button])

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auto_setup Rate-limited

auto_setup 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": {
    "auto_setup": {
      "limits": [
        {
          "counter": "auto_setup_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 Niscope, so you can run agents against it safely.

FAQ

Questions about auto_setup

What does the auto_setup tool do? +

Auto-configure the oscilloscope (equivalent to pressing. It is categorised as a Execute tool in the Niscope MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on auto_setup? +

Register the Niscope MCP server in PolicyLayer and add a rule for auto_setup: 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 Niscope. Nothing to install.

What risk level is auto_setup? +

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

Can I rate-limit auto_setup? +

Yes. Add a rate_limit block to the auto_setup 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 auto_setup completely? +

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

auto_setup is provided by the Niscope MCP server (ymzds/niscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

auto_setup is one line of Niscope's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →