Get hierarchical list of signals from waveform file
AI agents call get_signal_list to retrieve information from Waveform MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about available signals in a waveform file without side effects. It is a read-only operation that enables inspection of waveform structure, consistent with the 'Read' category for data retrieval with no side effects. The blast radius of misuse is minimal—an agent could enumerate signals but cannot modify hardware designs, execute code, or cause destructive changes.
From the tool's definition Tool name 'get_signal_list' and description 'Get hierarchical list of signals from waveform file' indicate retrieval of signal metadata. No modification, execution, or deletion occurs.
Documented attack patterns abuse exactly the kind of access get_signal_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waveform MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_signal_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_signal_list": {}
}
}get_signal_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get hierarchical list of signals from waveform file. It is categorised as a Read tool in the Waveform MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Waveform MCP Server MCP server in PolicyLayer and add a rule for get_signal_list: 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 Waveform MCP Server. Nothing to install.
get_signal_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_signal_list 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 get_signal_list. 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.
get_signal_list is provided by the Waveform MCP Server MCP server (ynivin/waveform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waveform MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Waveform MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.