create_track
Create a new conductor track directory with plan.md, index.md, and metadata.json. Fails if the slug already exists.
This record as markdown: /tools/2loch-ness6-mempalace-mcp-dev/create-track.md
What create_track does on Mcp Dev
AI agents use create_track to create or update resources in Mcp Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.
Why create_track is rated Medium
This tool creates new files and directories in the codebase structure (a track with multiple files and metadata). This is a reversible Write operation: the created artifacts can be deleted.
From the tool's definition Tool description states it 'Create[s] a new conductor track directory with plan.md, index.md, and metadata.json.' The verb 'create' and the explicit creation of file artifacts demonstrate a Write operation that adds new data to the codebase.
Attacks that exploit this kind of access
The rule that runs create_track safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_track, this is the rule to start with:
create_track 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every create_track call is checked against it from then on.
Questions about create_track
Create a new conductor track directory with plan.md, index.md, and metadata.json. Fails if the slug already exists. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for create_track: 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 Mcp Dev. Nothing to install.
create_track 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_track 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_track. 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_track is provided by the Mcp Dev MCP server (2loch-ness6/mempalace-mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue