set_signal_generator · PicoScope MCP Server MCP

WHAT IT DOES

What set_signal_generator does on PicoScope MCP Server

AI agents invoke set_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 set_signal_generator needs a policy

The tool name strongly implies it configures and activates a hardware signal generator on a PicoScope oscilloscope, which triggers an external physical operation (outputting electrical signals). This falls under Execute as it causes real-world hardware effects. Severity is high because misconfigured signal output could damage connected equipment or interfere with sensitive measurements.

From the tool's definition Tool name 'set_signal_generator' on a PicoScope MCP server that 'supports signal generation through natural language commands'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_signal_generator Rate-limited

set_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": {
    "set_signal_generator": {
      "limits": [
        {
          "counter": "set_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 set_signal_generator

What does the set_signal_generator tool do? +

set_signal_generator. 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 set_signal_generator? +

Register the PicoScope MCP Server MCP server in PolicyLayer and add a rule for set_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 set_signal_generator? +

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

Can I rate-limit set_signal_generator? +

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

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

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