export_waveform · PicoScope MCP Server MCP: Risk & Policy

WHAT IT DOES

What export_waveform does on PicoScope MCP Server

AI agents use export_waveform to create or update resources in PicoScope MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PicoScope MCP Server environment.

WHY IT NEEDS A POLICY

Why export_waveform needs a policy

Export operations create or modify data files/outputs, placing this in the Write category rather than Read (which would be passive retrieval). While not destructive (data isn't deleted), it writes/creates new data artifacts. Severity is medium because misuse could lead to unauthorized data exfiltration of oscilloscope measurements, though without financial or destructive consequences.

From the tool's definition Tool name 'export_waveform' combined with server context involving signal acquisition and data capture suggests exporting/saving waveform data. The empty description limits certainty, but 'export' typically involves writing data to external formats or storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_waveform Rate-limited

export_waveform stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_waveform": {
      "limits": [
        {
          "counter": "export_waveform_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 export_waveform

What does the export_waveform tool do? +

export_waveform. It is categorised as a Write tool in the PicoScope MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_waveform? +

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

export_waveform is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_waveform? +

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

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

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