This record as markdown: /tools/0xnullai-dg-mcp/load-waveforms.md
What load_waveforms does on DG-MCP
AI agents invoke load_waveforms to trigger actions in DG-MCP. 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 load_waveforms is rated High
This tool loads waveform/pulse pattern files from disk (a file path) and makes them available for use on a DG-Lab Coyote electrostimulation device. It involves file system access and side effects on the connected device's available waveforms.
From the tool's definition 从指定路径加载 .pulse 文件或包含 .pulse 的 .zip — loads waveform files from a specified path for use on a physical electrostimulation device
Attacks that exploit this kind of access
The rule that runs load_waveforms safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DG-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For load_waveforms, this is the rule to start with:
load_waveforms 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.
The button opens the PolicyLayer dashboard: create your workspace, connect DG-MCP, apply this rule, and every load_waveforms call is checked against it from then on.
Questions about load_waveforms
从指定路径加载 .pulse 文件或包含 .pulse 的 .zip。. It is categorised as a Execute tool in the DG-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DG MCP server in PolicyLayer and add a rule for load_waveforms: 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 DG-MCP. Nothing to install.
load_waveforms is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the load_waveforms 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.
Set action: deny in the PolicyLayer policy for load_waveforms. 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.
load_waveforms is provided by the DG MCP server (0xnullai/dg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DG, and thousands of servers like it.
This server
Across the catalogue