stop_signal_generator · PicoScope MCP Server MCP

WHAT IT DOES

What stop_signal_generator does on PicoScope MCP Server

AI agents invoke stop_signal_generator to trigger actions in PicoScope MCP Server. 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 stop_signal_generator needs a policy

This tool executes a command that halts an active hardware operation. While not destructive (the action is reversible by restarting the generator) and not inherently dangerous, it modifies external device state and could disrupt ongoing signal generation tasks if invoked incorrectly by an AI agent. The blast radius is limited to the connected oscilloscope, making it medium severity rather than high.

From the tool's definition stop_signal_generator stops signal generator output, which is an external operation that modifies the state of connected hardware (PicoScope oscilloscope).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_signal_generator Rate-limited

stop_signal_generator 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": {
    "stop_signal_generator": {
      "limits": [
        {
          "counter": "stop_signal_generator_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 PicoScope MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_signal_generator

What does the stop_signal_generator tool do? +

Stop the signal generator output. It is categorised as a Execute tool in the PicoScope MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_signal_generator? +

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

What risk level is stop_signal_generator? +

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

Can I rate-limit stop_signal_generator? +

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

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

stop_signal_generator is provided by the PicoScope MCP Server MCP server (markuskreitzer/picoscope_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.