AI agents use create_rack to create or update resources in Synthlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Synthlab environment.
This tool creates new Pd patch configurations and rack setups from natural language input. While it produces new digital artifacts (patches), these are reversibly stored data structures that can be modified or deleted. There is no execution of audio synthesis, no deletion of existing data, and no financial impact. The primary function is creating/generating new patch data, making it a Write operation.
From the tool's definition Tool description states "Generate an entire Eurorack-style rack of Pd patches at once" - the verb 'generate' combined with 'create_rack' name indicates creation of new configuration/patch data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Generate an entire Eurorack-style rack of Pd patches at once. It is categorised as a Write tool in the Synthlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Synthlab MCP server in PolicyLayer and add a rule for create_rack: 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 Synthlab. Nothing to install.
create_rack 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 create_rack 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 create_rack. 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.
create_rack is provided by the Synthlab MCP server (j0kz/synthlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →