sunvox_module_types
The SunVox module-type catalogue: every synthesizer/effect/controller type with its parameters (name, min, max, kind, default). This is the reference for writing sunvox_compose specs. Output exists automatically at module 0 — reference it as \
This record as markdown: /tools/kh0pper-crow/sunvox-module-types.md
What sunvox_module_types does on Crow
AI agents call sunvox_module_types to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sunvox_module_types is rated Low
Tool retrieves SunVox module metadata without modifying data or executing external operations.
From the tool's definition catalogue, reference, every synthesizer/effect/controller type with its parameters
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs sunvox_module_types safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sunvox_module_types, this is the rule to start with:
sunvox_module_types is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every sunvox_module_types call is checked against it from then on.
Questions about sunvox_module_types
The SunVox module-type catalogue: every synthesizer/effect/controller type with its parameters (name, min, max, kind, default). This is the reference for writing sunvox_compose specs. Output exists automatically at module 0 — reference it as \. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for sunvox_module_types: 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 Crow. Nothing to install.
sunvox_module_types 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 sunvox_module_types 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 sunvox_module_types. 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.
sunvox_module_types is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue