Select a sibling device (in the same chain as current device)
AI agents use select_device_sibling to create or update resources in Bitwig MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitwig MCP Server environment.
This tool changes the selection state within Bitwig Studio's device chain. It modifies the application's UI/selection state, which is a reversible write operation (selection can be changed back). It does not delete data, execute code, or involve financial transactions. The blast radius is low as it only changes which device is selected.
From the tool's definition Select a sibling device (in the same chain as current device)
Documented attack patterns abuse exactly the kind of access select_device_sibling gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitwig MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for select_device_sibling:
{
"version": "1",
"default": "deny",
"tools": {
"select_device_sibling": {
"limits": [
{
"counter": "select_device_sibling_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}select_device_sibling 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.
Free to start. No card required.
Select a sibling device (in the same chain as current device). It is categorised as a Write tool in the Bitwig MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitwig MCP Server MCP server in PolicyLayer and add a rule for select_device_sibling: 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 Bitwig MCP Server. Nothing to install.
select_device_sibling is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the select_device_sibling 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 select_device_sibling. 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.
select_device_sibling is provided by the Bitwig MCP Server MCP server (wemodulate/bitwig-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Bitwig MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Bitwig MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.